Docs Home
/
Developer Tools
/
Engine API

Engine API

What is it?

The Engine API is a web-based programming interface for software developers to interact with a new CAD kernel on powerful remote computers.

"What does the Engine API give developers that existing solutions don't already?" is a common question we get. To most, they don't know what "good" looks or feels like because they've been snow-blinded by the 40 years of incumbents' APIs.

Intuitive, first-class Web API

A first-class web API experience is at the heart of our Engine API. We make sure, at the raw protocol level, the API is as intuitive and easy to use. From there, our "API SDKs" add a little bit of programming language spice on top so it's even easier to integrate into projects. The layer of abstraction between the raw protocol and SDKs is so small that we're able to auto-generate them.

Whether you're a junior, seasoned, or an LLM developer, these human and LLM-friendly APIs significantly lower the barrier of entry to developing your own CAD tooling or generative & parametric CAD models.

Powerful Remote Compute

Laptops and mobile devices reign supreme in todays world. Lugging around a desktop to do high-end CAD work shouldn't be a requirement to get shit done.

Zoo offers all its CAD kernel instances on the best remote compute available. This means you can do real CAD work on your laptop's light form-factor. Its battery should live as long you can watch videos or play video games.

Always The Latest

In the past when new CAD kernels or programs become available, users are forced to download large gigabyte ZIP files to get the updates (and in some cases, pay for the package all over again!). Because a lot of the program logic lives on our servers, it removes the need to download huge packages.

At the same time, users of your application that uses Engine API will always get fixes and updates to our underlying CAD kernel in real-time. We're able to be responsive to bug reports and deliver fast bug fixes because we employ CI/CD in our development life-cycle.

What will you build?

Found a typo?