Object types
An organization’s object library shows only its own uploads. Platform objects are grouped into packs that an admin switches on, and appear when building a stage.
Supported formats
Org admins can upload models in any of these formats:
All uploads automatically produce a GLB for web preview and a USDZ for AR tracking where not already provided.
Making an object trackable
For an object to be tracked during a capture session, it needs a.referenceobject file, an Apple ML-trained descriptor of its geometry generated from the USDZ mesh.
The platform handles this as a processing request. When an admin links a non-trackable object to a skill, a request is automatically filed. The Holos team processes it and uploads the resulting .referenceobject file.
Key fields
Representations
A large model carries lighter versions of itself alongside the full one, so a client can fetch what its own triangle budget allows rather than always taking the largest file.source.glb and source.usdz remain the full-fidelity version, and source.representations holds the rest.
A client picks the coarsest level under its own budget. Levels are produced only where they earn their place, so a model light enough already carries none.
Endpoints
GET /objects: list objects (platform + org-private)GET /objects/{objectId}: get an objectPUT /objects/{objectId}: update name, tags, and other editable fieldsPUT /objects/{objectId}/approval: set approval statusPOST /organizations/{id}/objects/upload: initiate an org object upload
