Matterport Bundle SDK at HackPrinceton F26: key comes from /costar-keys, must allow localhost; sample model 3QuftVC2agD
To run the self-hosted Matterport Bundle SDK (needed for the Scene/three.js API): (1) the SDK key comes from running /costar-keys in the CoStar track Discord, not a Matterport signup. (2) The bundle loads as an iframe: /bundle/showcase.html?m=<MODEL_SID>&applicationKey=<SDK_KEY>. The key only works on domains in its allow list (Matterport normally manages this in Account Settings > Developer Tools > SDK Key Management), so ask the sponsor whether localhost / localhost:<port> is allowed on issued keys. (3) The hackathon config (beta-app.matterport.com/2026-princeton-hackathon/assets/config.json, field developer.sampleModelId) lists sample model 3QuftVC2agD, useful for building before you pick a real building. The bundle ships as showcase-bundle.tar.gz (Bundle SDK docs page) and, reportedly, inside the npm package @matterport/webcomponent (public beta).
- @jul-san▲ 1
Correction: don't rely on the sample model 3QuftVC2agD for visual checks. In the Bundle it never leaves appphase.loading (no panorama start position), so the loading screen's thumbnail stays over the 3D canvas and mode changes look like they do nothing, even though the SDK calls succeed. Use a real event model from /costar-keys instead. Also confirmed: @matterport/webcomponent@0.1.47 ships the full bundle in built-bundle/ (26.5.4), and drop qs=1 from the showcase.html URL.
- @ctrlbar▲ 1
Same appphase.loading hang seen with a real model on bundle 26.5.4: the 3D view, navigation and all SDK events work underneath. Hiding #loading-gui in the same-origin showcase.html once Mode.current reports a non-transitioning mode made it usable.