Technical drawings for your software and your AI agents

The same drawing engine as Occlusia Studio, run on Occlusia’s servers behind a REST API and an MCP server. Send a 3D model and a configuration; get plans, sections and elevations back as DXF, PDF, SVG, PNG or JPEG — the drawings Studio makes, byte for byte.

The REST API

Every request carries an API key or an OAuth access token. A session is an engine of your own, with its own files: upload, run commands, download, end it.

https://api.occlusia.app/v1/engine

KEY=occ_sk_…                                  # Account › API keys
API=https://api.occlusia.app/v1/engine
AUTH="Authorization: Bearer $KEY"
JSON="Content-Type: application/json"

# 1. A session: an engine of your own, with its own files
S=$(curl -s -X POST $API/sessions -H "$AUTH" | jq -r .id)

# 2. The model and your graphic standard
curl -T house.skp $API/sessions/$S/files/house.skp -H "$AUTH"
curl -T standard.occc $API/sessions/$S/files/standard.occc -H "$AUTH"

# 3. Open the model (1 credit), apply the configuration (free)
curl $API/sessions/$S/commands/model.open -H "$AUTH" -H "$JSON" -d '{"path":"house.skp"}'
curl $API/sessions/$S/commands/config.set -H "$AUTH" -H "$JSON" -d '{"path":"standard.occc"}'

# 4. Export one view as DXF (1 credit per drawing)
curl $API/sessions/$S/commands/export -H "$AUTH" -H "$JSON" \
     -d '{"format":"dxf","sections":"Section A-A","out":"section-a.dxf"}'

# 5. Download it, then end the session: its files are deleted with it
curl -o section-a.dxf $API/sessions/$S/files/section-a.dxf -H "$AUTH"
curl -X DELETE $API/sessions/$S -H "$AUTH"

The whole API in OpenAPI at /v1/engine/openapi.json, and every command with its JSON Schema at GET /v1/engine/commands. REST API guide

One engine behind Studio, the API and MCP

A program gets what a person gets in Studio: the same drawings, the same refusals, the same prices. The API names the engine’s version and build at GET /v1/engine.
Open models
SketchUp (.skp), IFC and FBX models, Occlusia’s own .occs models and .occp projects.
Read them
Objects and their groups, views, notes, spot elevations, layers, line styles and hatch presets.
Style them
Any setting of an object, a view, a note or a layer — or a whole .occc configuration, checked before it is applied.
Preview
A view as PNG, JPEG or SVG, up to 2048 pixels on its longer side: what an AI agent looks at.
Export
SVG, DXF, PDF — a page per view or one document, with its paper, orientation and scale — PNG and JPEG.
Auto config
The configuration Occlusia proposes from the objects’ names, quoted before it runs.

The MCP server, for AI tools

Over Streamable HTTP. An AI tool needs only the address: the first time, it sends you to occlusia.app to approve it, then comes back with a token. There is no key to copy.

https://api.occlusia.app/v1/mcp

Claude
Settings › Connectors › Add custom connector, then the address.
ChatGPT
Add a custom MCP server with the address, and OAuth as its authentication.
Cursor, VS Code and others
Add a remote MCP server (Streamable HTTP) with the address: they sign you in the same way.

Claude Code: one command, then /mcp to sign in — or the same with an API key, for tools that send a header.

claude mcp add --transport http occlusia https://api.occlusia.app/v1/mcpclaude mcp add --transport http occlusia https://api.occlusia.app/v1/mcp \
  --header "Authorization: Bearer occ_sk_…"

MCP guide

Paid in credits, like Studio

Exports and Auto config cost what they cost in Studio. Because Occlusia’s servers do the work your computer does in Studio, opening a model costs 1 credit and each new drawing computed 1 credit; the same drawing again in the same session is free, and so are listing, reading and settings. Every paid answer says what it cost and the balance after.

During early access nothing is taken, up to 500 credits’ worth of API work per account in any 24 hours.

How credits work

Going further

Building Occlusia into your product?

Dedicated technical accounts, custom limits, white-label and OEM use are agreed separately, in writing.