Two honest answers to “make me a 3D model with AI”. Meshy generates the mesh; antics-modelkit writes code that builds it. Modelkit is ours — read this the way you'd read any maker's comparison. Everything we say about Meshy below comes from their public site.
From a concept image, Meshy produces a mesh with a full PBR texture set — albedo, normal, metallic, roughness — in under a minute, exports to GLB, FBX, OBJ, USDZ and more, and can auto-rig and animate characters. For a hero prop, a creature, or anything whose job is to be looked at, it is the fastest route we know of, and this page won't pretend otherwise.
A generated mesh is finished the moment it exists — to change it you regenerate and hope,
or open a modelling app. A recipe is never finished: the crate's width is a number, the
watch lid is a part named lid your game can open, and next week's “make
it 20% wider” is an edit, not a do-over. A set of models shares one palette and one
style because it shares one file, and the whole thing lives in git like the rest of your
game.
| antics-modelkit | Meshy | |
|---|---|---|
| What you get | A code recipe + a checked .glb | A generated, textured mesh |
| Editing afterwards | Change a number, rebuild | Regenerate, or edit in a modelling app |
| Named parts | Every part, by design — games address them in code | Not publicly documented |
| Textures | Flat colours per part — stylised, low-poly | Full PBR set: albedo, normal, metallic, roughness |
| Rigging & animation | No rig — parts are moved in code | Auto-rig and animate characters |
| A matching set | One recipe style, shared numbers across models | Each generation is its own one-off |
| Version control | Recipes diff like any source file | Binary meshes |
| Export formats | .glb, plus the MIT recipe | GLB, FBX, OBJ, USDZ, STL, 3MF |
| Price | Free, MIT — no credits, no account | Free: 100 credits/mo, output CC BY 4.0 · paid from $20/mo, you own the assets |
Meshy details verified against meshy.ai's public pricing and feature pages, August 2026. Where their docs don't say, the cell says so rather than guessing.
Pick Meshy when the asset is the destination: a textured hero piece, a creature, a one-off you'll place and admire. Pick modelkit when the asset is part of a game: a set that has to match, parts you'll animate from code, dimensions you'll still be tuning next week. A player in our launch thread put it better than we did — mesh generators didn't give him “the consistency you need” for a game's asset set. That's the line between the two tools.
For game props and matching sets, yes — a free, MIT-licensed one. For textured organic hero pieces it isn't; that's Meshy's home turf, and a code recipe won't get you a photoreal dragon.
Comfortably. Both export .glb, so a Meshy hero piece and a modelkit prop
set load into the same Godot, Unity, Unreal or browser scene the same way.
Differently: give your agent a reference photo and it models what it sees, in code — our pocket watch was built from a single photograph. It reconstructs by reasoning, not by scanning, which is why the result comes back editable.
Because an AI can't edit a mesh, but it can edit a number. If an agent is building your game, code is the one format it can read back, reason about and change without starting over. The modelkit page shows what that looks like.