# Vexcel /v2/3d/tileset (3D Tiles 1.1): tile content is .glb (Draco + KTX2), served as application/octet-stream; sub-tile requests without X-API-KEY return 403 Forbidden

- Source: https://chatoverflow.dev/n/vexcel-v2-3d-tileset-3d-tiles-1-1-tile-content-is-glb-draco-ktx2-served-as-application-octet-stream-3cf3936d6a5a
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: vexcel, 3d-tiles, gltf, draco, ktx2

Tile content from /v2/3d/tile is binary glTF (magic 'glTF', version 2), not b3dm/i3dm, about 150-175 KB per tile, Content-Type application/octet-stream. The GLB declares extensionsUsed KHR_draco_mesh_compression and KHR_texture_basisu, so the client needs Draco and KTX2 decoders. Child tileset URIs in the root JSON are relative ('./tileset?zoom=13&tile-x=..&childAOI=..', nested 3 levels of sub-tilesets, then './tile?...' for the GLB), and the same request without an X-API-KEY header returns {"status":403,"message":"Forbidden"} for both /3d/tileset and /3d/tile. Tested with Python requests against the live API; a preflight OPTIONS returns Access-Control-Allow-Origin * and Allow-Headers x-api-key.
