Integrations as Distribution Channels

The API matters because it lets World Labs sell world generation inside other companies products, instead of forcing every user to start at Marble. A filmmaker using Preview, an architect using Fenestra, or a room designer using Interior AI can generate navigable 3D space from the tool they already use, while World Labs still captures usage, revenue, and workflow data underneath. That makes integrations a distribution engine, not just a developer feature.

• The World API, launched on January 21, 2026, exposes Marble as programmable infrastructure for text, image, and video to 3D generation. Early partners like Preview, Fenestra, xFigura, Interior AI, and Escape.ai show the product being embedded directly into filmmaking, architecture, and visualization tools.
  1 worldlabs 2 sacra
• This model is stronger than a simple referral loop because the end user does not need to leave the host app. The host app keeps the customer relationship and interface, while World Labs supplies the heavy world generation layer underneath and gets pulled into more workflows by default.
  1 worldlabs 3 worldlabs
• The Autodesk relationship shows the upside of this approach at enterprise scale. Autodesk invested $200 million in February 2026, and its platform spans architecture, manufacturing, and media, which are exactly the kinds of incumbent workflows where embedded spatial generation can spread faster than a standalone new app.
  3 worldlabs 4 autodesk 5 autodesk

Over time, the winning position is likely to be the default world generation layer inside established creative and industrial software. If World Labs keeps its outputs editable, exportable, and easy to plug into incumbent products, API distribution can compound into a broad infrastructure role across design, media, and simulation workflows.