About Open3DAI
A multi-engine front end for AI 3D generation, built around one input, one credit pool and an honest capability list.
Why this exists
Choosing an AI 3D engine used to mean committing to one. Each service had subjects it handled badly, and the only way to find out whether a prompt would work was to pay for a second subscription and try again on another site.
Open3DAI puts the engines behind one input. Write a prompt or upload a photo once, run it through the local engine and any configured third-party engine, and look at the meshes side by side in the same viewport before deciding which one to keep.
What we will not pretend
The built-in engine is procedural, not a trained neural network, and that is stated in the Studio rather than hidden. Third-party engines run only when an operator has configured their API keys; until then they show as not configured and no request is sent to them.
The 48 converters work on mesh formats. CAD and DCC native formats — STEP, IGES, SLDPRT, X_T, DWG, SKP, IFC and BLEND — have no open Python reader here, so those pages say so plainly and offer an alternative path instead of a fake success message. FBX and USDZ are read in the browser where an open parser exists.
How it works
One input
text, a single image, two or more images for multiview, or a folder for batch. The same four modes on every engine, so a comparison isolates the engine.
One credit pool
a standard generation is about 10 credits, texturing about 4 more, HD texture 4 again. Each engine in a comparison charges the base cost, and every charge lands in a per-engine ledger.
One viewport
ten shading modes, identical for every engine, with dimensions, volume, surface area and watertight status reported for each result.
One export step
GLB, glTF, OBJ, STL, PLY and 3MF on every plan, including Free, with 48 server-side converters for the formats around them.
One API
API keys with scopes, idempotency keys, webhooks and hourly rate limits, so the same workflow can run without a browser.
How we handle the third-party engines
Tripo3D, Meshy, Rodin and Hitem3D are separate companies and separate services. They are reached through adapters, they are named on their own pages, and the site is not affiliated with them. Their names are trademarks of their respective owners, which is stated in the footer as well.
When a request is routed to one of them, the prompt or image needed for that request is transmitted to that provider under its own terms. The local engine requires no such transfer, which is why it is always available and always the fallback.