IngestOne path in, whatever the source
A person uploads in the browser, or an agent submits a model from a URL and finalises the upload through the API. Signed upload URLs keep the storage credentials out of the client, and nothing reaches the catalogue until the file has been checked.
Browser uploadUpload APISigned URLsGLB validation
ProcessingClean, web-ready files, generated automatically
Geometry is quantized and textures are re-encoded to WebP and embedded, so every model is a self-contained binary glTF that three.js loads without Draco or KTX2 decoders. The same run produces thumbnails, posters, a blurhash placeholder and the stats shown on each asset page.
GLBKHR_mesh_quantizationWebP texturesPreviews
ReviewA human before anything goes live
Processed assets queue for review. A person checks the model and its metadata, the contributor acceptance of the CC0 dedication is recorded, and any AI involvement is attributed to a named model. Versions are kept, so a correction never breaks an existing link.
Review queueCC0 1.0AI attributionVersioning
DeliveryImmutable CDN URLs you can hotlink
Published files live at a versioned, immutable URL on the CDN, served with CORS open to every origin and no cookies or keys. A model is downloaded once and cached, rather than re-fetched on every build.
CDNCORSImmutable URLsRate limits
CatalogueBrowsing that suits people and packs
Every asset is filed by category, theme and style. Packs group models that share a palette, scale and materials, and each one ships a composed starter scene and a manifest of individual CDN URLs alongside a walkable demo.
Next.jsSearchPack manifestsWalkable demos
AgentsMCP and REST, not an afterthought
The whole catalogue is readable through a streamable HTTP MCP server and a versioned REST API, with per-asset Markdown, llms.txt and a skill for agent clients. Reads need no account or key; writes use a bearer key tied to the contributor.
MCPREST API v1OpenAPIllms.txtSKILL.md