Is there an API for rendering?
Yes. A single REST endpoint takes an image and a prompt and returns a render in about 30 seconds, authenticated with a bearer token and billed from the same credit balance.
The API is deliberately small. You POST to /api/v1/render with an image, a tool name — sketch_to_render, interior or exterior — and a prompt, authenticate with an API key from your account, and get render URLs back. There is no SDK to install and no separate billing account; calls draw from the same credit balance as the web app.
The most common uses are internal rather than product-facing: batching a folder of viewport captures overnight, wiring rendering into a project portal so that project managers can produce images without learning the tool, or generating listing imagery from a property system. The SketchUp and 3ds Max plugins are themselves nothing more than small clients for this endpoint, which is a reasonable indication of what it can carry.
On the free tier every API call costs 30 credits regardless of the tool, which makes it usable for testing but not for volume. On paid plans the real per-tool price applies.
Rate limits and terms for high-volume or product-embedded use sit under the Enterprise plan. If you are building the API into something you sell, that is the conversation to have rather than scaling up a self-serve plan quietly.
Try it on your own project
100 free credits to start, no credit card. You will need an image to start from — a plan, sketch, photo or viewport capture.