Occlusia’s drawing engine, inside your product

For software publishers, AI platforms and organisations that generate technical drawings at scale or under their own brand. The REST API and MCP are available today; anything beyond the standard terms is agreed with you, in writing.

What any account can use now

No agreement is needed to start: the API and MCP are open to every account, as the developers’ page describes.
REST API and MCP
The same drawing engine as Occlusia Studio, run on Occlusia’s servers, for scripts, servers, CI jobs and AI tools.
OAuth 2.1
An app of yours can act for its users, each with their own Occlusia account and credits.
Standard limits
3 sessions per account, 2 computations at a time, 600 requests a minute per key, 512 MB per file.
Public price list
Paid in prepaid credits that never expire, without a subscription.

How licensing works

Occlusia’s Terms of Service grant each account holder a personal, non-transferable licence for their own work. They do not allow redistributing, sublicensing, selling or renting the application, its engine or the API, nor giving others access to the service through your account or your keys.

Organisational use, technical accounts serving end users, white-label use, OEM distribution, redistribution and sublicensing, quotas, processing capacity, support, service levels, responsibilities and intellectual property are therefore covered only by a written agreement signed with Occlusia’s publisher — and only to the extent it expressly says so.

Nothing on this page grants any of these rights: it describes what can be discussed.

Contact

Let’s talk about your integration

Write to hello@occlusia.app with a few lines about your project. Every message gets an answer.