

Industrial CAD kernels over plain HTTP
The kernels behind our editors, running on managed compute. Call them from your backend in any language, from a nightly batch job, or from your AI coding agent, and download the result as STEP, glTF, STL or JSON.
Running a geometry kernel in the browser is the right answer for an interactive configurator, and the wrong answer for a nightly batch of ten thousand parts, a quoting service that must not trust the client, a serverless function that cannot host a kernel, or an AI agent that has to hand you a file rather than code. Those belong on a server, and until now that meant licensing a desktop CAD kernel and operating it yourself.
CAD Cloud is that server. You send a request, it runs on managed compute, and you download the result in the format you need. 1060 of the algorithms you use in the editors and in the open-source packages - the OpenCascade, JSCAD, Manifold and Verb kernels, every math, vector and list helper - run there too, without hosting anything.
Node, Python, Go, Java, .NET or anything else that can make a request. Generate a model from parameters, convert a STEP file, run a pipeline, download the result. A TypeScript SDK and an OpenAPI 3.1 specification are published for every endpoint.
API guideConnect the Bitbybit CAD Cloud MCP with a key and your agent runs the same operations from Claude Code, Codex, Cursor or VS Code. Ask for the volume of a STEP file, its bounding box, a filleted box as STEP or a sheet-metal flat pattern, and get the number or the file back.
CAD Cloud MCP guideBatch conversions, quoting, manufacturing exports and everything that runs unattended. Every job is a task with a status you can poll, retry or cancel, and results you download through pre-signed links.
Watch tasks in Bitbybit Studioocct.shapes.solid.createSphere.Every request is asynchronous by design, because real CAD work is not measured in milliseconds. You submit a job, receive a task id, poll for completion, and download the result as STEP, glTF, GLB, STL, a decomposed mesh or JSON. That model holds whether the job takes two seconds or two minutes, so a slow operation never becomes a timed-out HTTP request.
Authentication is an x-api-key header on every endpoint except the health check. Keys are scoped, so a key issued for conversions cannot be used to run arbitrary kernel operations, and an agent sees only the tools its key allows.
npm install @bitbybit-dev/cad-cloud-sdk
claude mcp add --transport http bitbybit-cloud https://api.bitbybit.dev/mcp --header "X-API-Key: <your key>"The whole surface is described by a published OpenAPI 3.1 specification, so you can generate a client in any language, import it into Postman or Insomnia, or hand it straight to an AI coding assistant. A first-party TypeScript SDK is on npm if you would rather not generate one, and two MCP servers cover the agents: a free one that documents the API, and this keyed one that runs it.
The project CLI sets up a full-stack application with the API already wired in. Choose the CAD Cloud option and you get a backend - Hono on Cloudflare Workers, Node.js with Express, or ASP.NET Core - and a React and Three.js frontend that proxies requests through it, so your API key never reaches the browser.
npx @bitbybit-dev/create-app my-project