Gaitkit Open the lab
Live specimen · loading

Describe it. It walks.

3D models written as code. Type what you want and the specimen re-forms on the spot, still walking, rolling or swinging its doors. Your AI agent gets the same words over MCP.

Colours, sizes, parts, night. English or Turkish.
Works with three.js, React Three Fiber, Godot, Unity, Blender and anything that reads GLB.
Waking the specimens…
Drop it on the ground

Forging0:00

    drag to orbit · tap the ground to send it
    01 · Moving parts

    Walk. Roll. Open.

    Motion ships inside the specimen. The build measures it before anything is published and turns away whatever slips. Drag any of these to look around.

    Walk foot slide 0.00 mm

    Every leg is a two-bone IK chain. Steps are timed by distance covered, not by the clock, so a planted foot stays planted at 30 fps, at 144 fps and in an offline render. More than a millimetre of slide and the build fails.

    Roll no wheel skid

    Wheels are their own parts and turn exactly as far as the car travels. In three.js that is one call, tick(distance); every other engine gets a baked loop clip in the GLB.

    Open real hinges

    Doors, lids and turrets pivot where the hinge actually is, and the swing range is written into the metadata. Windows and lanterns switch on after dark.

    02 · Workflow

    Pick. Tune. Ship.

    01

    Pick by behaviour

    Filter by what a specimen does, not only by what it is. Every card carries its real size in metres and its triangle count, so you know what fits before you load it.

    walksdrivesopensglows at night
    02

    Tune in words or knobs

    Each knob is typed and carries a one-line description. That line is the vocabulary: you drag a slider, your agent says "long legs", both land on the same value.

    // "yellow spider, long legs, 4 eyes"
    colorway  "hazard"   black/yellow
    legLength 1.25       0.75–1.4
    eyes      4          2 | 4 | 8
    03

    Ship it moving

    Import the module and call it with your knob values, or download a GLB with the motion already baked in.

    const bot = createAsset({ legLength: 1.25 });
    const gait = walker(bot, { ground });
    // per frame
    gait.poseAt(distanceTravelled);
    ES moduleGLB + clipOBJFBX nextUSDZ next
    03 · For agents

    Your agent speaks knob

    Point Claude Code, Cursor or Codex at the Gaitkit MCP endpoint and it can search the drawer, turn a sentence into knob values and place the result. The terminal below is not a recording: it runs the same matcher the server answers with, here in your browser.

    Claude Code
    claude mcp add --transport http gaitkit https://gaitkit.com/mcp
    Cursor, Codex, any MCP client
    { "mcpServers": { "gaitkit": {
      "type": "http", "url": "https://gaitkit.com/mcp" } } }
    Four tools, no key to browse
    search_assetsFinds specimens and grades its own answer: ok, poor or none. A wrong match is worse than an honest gap.
    get_assetSize in metres, palette, knob schema, gait data and paste-ready three.js.
    get_variant"arctic mech with twin guns" in, a createAsset() call and a confidence level out. English or Turkish.
    report_needLogs what was missing. The request queue is the factory's to-do list.
    Install for Cursor, Codex, VS Code and Windsurf →
    04 · Catalogue

    Fresh from the forge

    Every specimen here cleared the validator: real-world scale, one material, a triangle budget and, for walkers, feet that stay where they land. Drag a card onto the stage at the top to add it to the scene.

    05 · On the bench

    Kits that share a world

    A kit is 25 to 60 parts cut to one palette and one scale, so a scene assembled from it reads as a single place. These are being forged now; a part joins the catalogue the day it passes.

    06 · Why code

    Mesh or specimen

    A mesh from an asset storeA Gaitkit specimen
    A different colour or sizeBack to Blender, edit, export againChange a knob or a word; it rebuilds in the browser or in your code
    MovementRig it, then hunt for clips; anything with more than two legs is on youWalks, rolls or opens as delivered; the GLB carries a baked clip
    Slopes and stepsFeet sink or hoverIK plants each foot on your terrain; slide is measured in millimetres
    Twenty variantsTwenty filesOne module, twenty knob sets, identical output every time
    Handing it to an AI agentA black box it can only moveTyped knobs with descriptions, searchable and settable over MCP
    WeightMegabytes of mesh and texturesA module of a few KB, one material, one draw call
    07 · Pricing

    Free to explore. Cheap to own.

    The lab, every knob and the agent tools are open to everyone. Paying unlocks the whole drawer for download.

    Explorer

    $0
    No account needed.
    • Roughly a third of the specimens to download, knobs intact
    • ES module and GLB, fine for commercial work, no credit line required
    • Load straight from our CDN
    • All four agent tools and the REST API
    Start in the lab

    Pro

    $12/month
    Cancel whenever · or $96 a year
    • The full drawer, plus every specimen the factory adds
    • Bake any knob combination into a download
    • Every export format and a personal CDN token
    • Your three specimen requests a month jump the queue
    • What you downloaded stays licensed if you stop paying
    Get on the launch list

    Founder

    $79 one time
    Pro for good · launch window only
    • Everything Pro gets, now and later
    • Pay once, never renew
    • Your name engraved on the founders' page
    250 seats · open for 60 days from launch

    Students, and anyone for whom this costs a week's groceries: half price, just ask. First purchases are refundable for 14 days, no questions. Compare plans and billing details

    The spider that started the bench

    Gaitkit began with one robot spider. I was making a mixed-reality game and needed a creature whose feet found the real floor of a living room. The stores sold me statues: good-looking meshes that could not take a step, and rigging anything with more than two legs ate days per creature.

    So I wrote the walker as code, and the rest of the bench followed: crabs, beetles, mechs, cars whose wheels never skid, cottages with doors on real hinges. Gaitkit is that bench with the doors open. If the specimen you need is missing, type it into the box at the top. Those requests decide what gets forged next.

    — Ümit, maker of Gaitkit · github.com/algorr

    08 · FAQ

    Asked so far

    What is in a download?

    The specimen's ES module (it returns a three.js group), its knob schema as JSON, a GLB with a baked Walk or Loop clip when it moves, an OBJ, a README that lists every knob, and the licence text.

    Do I have to rig the creatures?

    No. Legs arrive as named joint chains and the IK solver is a free runtime file. In Unity or Godot you can play the baked Walk clip, or port the two-bone solver from the leg data in the metadata; it is about thirty lines.

    Is the box at the top the same thing my agent uses?

    Yes. The page imports the matcher module that the MCP get_variant tool runs on the server. It reads each knob's description, so it learns new words whenever a specimen ships.

    Can I sell what I make with them?

    Yes: games, apps, client work, courses and products, without a credit line. What you cannot do is resell the specimens as assets, serve them to your own users without a Platform licence, or feed them to a commercial model generator.

    Which engines work?

    three.js r150 and later and React Three Fiber run the modules directly. Godot, Blender and other glTF tools import the GLB. Unity reads the GLB through glTFast today; FBX and USDZ exports come next.

    The thing I need is not here. Now what?

    Describe it in the box at the top, ask from the lab, or let your agent call report_need. All three land in the same queue, and the queue is what the factory builds from.