# Laydyne

> A browser tool for floor plans and 3D layouts that your own AI edits over MCP, with layout comparison and queue and robot simulation.

Laydyne (https://laydyne.com) is a browser tool for floor plans and 3D layouts of one or several levels. Your own AI (ChatGPT, Claude, Codex, Claude Code or any MCP client) builds and revises the model over MCP, or you edit it by hand in Studio; it compares layout options under the same conditions, simulates people, goods and robots, and exports drawings, quantities and the project file.

Prices (US dollars before tax): Free, $0: modelling, editing over MCP, checks, 2D drawings, 3D images, browser saving and JSON import and export, with no count limit; a free account is needed for an MCP link (3 per account). Pro, $29 a month or $278.40 a year, and Max, $89 a month or $854.40 a year: simulation runs, the built-in AI and cloud saving. Your AI provider bills its own usage separately. Details: https://laydyne.com/docs#plans
Inputs: a text brief; drawings as PNG, JPEG, WebP or PDF files up to 5 MB, placed as a scaled underlay; photos, with the camera solved from marked points; GLB models of furniture and equipment; Laydyne project JSON. DWG, DXF and IFC files are not imported.
Outputs: scaled 2D drawings as SVG, PNG or PDF with an issue register; 3D images from named viewpoints; HTML and PDF reports and a proposal packet; areas and quantities; the project as versioned JSON with a public schema; a GLB of the static meshes.
Not calculated: Results come from a simplified, deterministic model: robots are circles moving at constant speed, and the same input always gives the same result. It does not model collisions or avoidance between robots or people (only capacities and queues), crowd physics, optimised lift group control (lift cars follow simple fixed rules), turning, or cleaning quality. Batteries, when a scenario gives them, drain in a straight line and charge at a constant rate. Dimensions read from photos and drawings are assumptions to check against measurements. It is for exploring options, not a calibrated prediction of a real site.
Connect: add the MCP server https://laydyne.com/api/mcp/oauth to your client and sign in with a free Laydyne account; the work is saved in an AI workspace on Laydyne, which the user opens in Studio. Client steps: https://laydyne.com/docs#connect-mcp
What Laydyne can do, feature by feature, with the files it produced: https://laydyne.com/features
What it does for a kind of work (office interior design, furniture proposals, store planning, event venues, warehouse robots, facility management), with an example to open and the files it produced: https://laydyne.com/for

For floor-plan navigation, set_space_view accepts dimension="2d", scope="building", planLayout="all-levels" for equal-scale sheets of every level, or planLayout="level" for the active level layout. Use scope="floor" for active-area editing and playback. These settings preserve geometry and are saved with the project. The UI labels are 2D plans / 3D model, All levels, Level layout and Edit area.

The plan and perspective views describe one project. Geometry consists of floor outlines, holes, extruded footprints, heights and explicit floor connections, not arbitrary free-form meshes.

## For AI agents
- [Full guide for agents](https://laydyne.com/llms-full.txt): how to connect, the working rules and starting prompts.
- [Claude Code skill](https://laydyne.com/agents/laydyne/SKILL.md): save as ~/.claude/skills/laydyne/SKILL.md.
- [Codex AGENTS.md section](https://laydyne.com/agents/AGENTS.md): add to your AGENTS.md.
- Once connected, the MCP server also offers the starting prompts (prompts/list).

## Authoritative product information
- [Manual](https://laydyne.com/docs): setup, tools, project persistence, simulation methods and limitations.
- [Example library](https://laydyne.com/examples): editable projects, synthetic inputs, recorded engine output and project JSON downloads.
- [AMR line supply study](https://laydyne.com/examples/amr-line-supply): one AMR, two AMRs and a closer pickup under the same 48 requests. Recorded 2D/3D playback includes loaded/empty states, current queues and a final comparison. Relocated staging excludes upstream replenishment costs.
- [Office layout change](https://laydyne.com/use-cases/office-layout-change): an existing office floor, current layout A against proposal B in the same view, the client's revision R02, and A3 plans, quantities and a proposal PDF from the same saved version; synthetic floor, no forecast.
- [Apparel retail](https://laydyne.com/use-cases/apparel-retail): fitting/checkout capacity and stockroom replenishment.
- [Warehouse transport](https://laydyne.com/use-cases/warehouse-transport): connected floors and service capacity.
- [Venue flow](https://laydyne.com/use-cases/venue-flow): arrivals and registration queues, not crowd safety.
- [Venue layout options](https://laydyne.com/use-cases/venue-layout): a seated and a standing plan of an invented event hall, revisions, seat and equipment counts, and a proposal packet; synthetic data, no forecast.
- [Office cleaning](https://laydyne.com/use-cases/office-cleaning): simplified reachability and coverage.
- Each use-case page ends with five short questions (what the workflow does, the inputs, the outputs, what it does not calculate, what it costs and what is free) and carries BreadcrumbList and FAQPage JSON-LD with the same sentences; the office layout page also describes its four stages as HowTo steps. The manual's plans section (https://laydyne.com/docs#plans) repeats its four price questions as FAQPage.

## Access
Free: 2D/3D editing, route checks, browser saving and full project JSON import/export. External MCP modeling requires a free account. Sign-in connections work in an AI workspace saved on Laydyne, which the user opens in Studio; no Studio tab needs to stay open. Pictures, 3D views, PDF and simulations need the workspace open in Studio. Agent links need the linked Studio tab to stay open. The MCP client has its own provider costs. Current prices, limits and data locations: https://laydyne.com/docs#plans
After a spatial process run, set_space_view with playbackTarget="process" controls play/pause, timeSeconds and playbackSpeed without recalculation. Read get_space.processResult.playback for duration, stale state and trace truncation. Target defaults to the current playback; playbackTarget="robot" selects cleaning/transport. Stale results or results without agent traces cannot be replayed.
Large rule-based models can be generated by a program: get_project_schema returns the saved project format as JSON Schema with its coordinate and id rules, and https://laydyne.com/sdk/laydyne-kit.mjs (types: /sdk/laydyne-kit.d.ts) is a dependency-free Node.js kit that builds floors, buildings, connections and scenarios and checks them with the app's own schemas. apply_changes then puts or removes whole floors, buildings, connections and scenarios by id (dry run first; fingerprints refuse items edited in Studio since), leaving everything else as it is. Free.
Pro: simulation execution (including MCP), built-in AI and manual cloud project saving. Availability depends on account access; public recorded examples are not a simulation execution entitlement.

## Decisions and business value
The examples explain who uses the result, which staffing/equipment/layout decision it supports and which site measurements are needed. The apparel project separates checkout-only, fitting-room-only and combined capacity changes into four options. Workflow results are operational measures, not automatic revenue or cash-saving forecasts. Time released for other work differs from reduced paid hours. See [From a result to a decision](https://laydyne.com/docs#business-value) for a clearly hypothetical time-and-cost calculation. The separate cleaning/transport robot comparison supports user-supplied cost assumptions; it does not validate them against a real site.

## Evidence boundary
Examples are synthetic, not measured forecasts. Published results specify inputs, seeds and engine version. Public animation replays recorded traces. Queues share a point; the model does not simulate physical crowd spacing, collision avoidance, evacuation safety, lift dispatch, revenue or inventory depletion. Review the manual before treating a result as evidence for an operating site.