Who it is for
Built for the products cutting rooms already use
A good nesting engine takes years to build and never stops needing work. Lescut is that engine, kept current for you, so your team can spend its time on what makes your product yours.
CAD and pattern software
Your users draw the parts in your software. Add a Nest button that sends them with the hides, roll or sheets and draws the result in your own view.
Cutting machine makers
Knife tables, lasers, routers and waterjets. Ship nesting with the machine, so the DXF your customer cuts comes out already nested.
Scanner and vision makers
Your scanner already knows the hide’s outline, defects and grades. Send them with the order and hand back a nest, not just a scan.
ERP, MES and resellers
Offer nesting to the manufacturers you serve, inside your product or as a branded app, with prices you set on partner terms.
Cloud REST API
How nesting works through the API
The same engine that runs the Lescut app, behind one HTTPS interface with an OpenAPI document. Anything that can call HTTPS can use it: no SDK to install, no native library, no platform to match. Generate a client in any language from the OpenAPI document, or call it directly.
- 01
Your software sends a job
Parts as outlines in mm with holes, quantities and grain, flip and grade rules; the hides with defects and grade zones, a roll width, or sheet sizes and counts; the number of sets and a time limit.
- 02
We nest it in the cloud
Each job runs on a dedicated, powerful cloud machine, up to 10 side by side. Poll the job for the best nest so far, so your users watch the yield climb and can stop early.
- 03
The nest comes back
Placements for your software to draw, one DXF and SVG per hide, sheet or marker with the original layers and curves, and a CSV of which part is cut from where.
curl https://lescut.com/api/v1/jobs \
-H "Authorization: Bearer $LESCUT_KEY" \
-H "Content-Type: application/json" \
-d '{
"parts": [
{ "name": "Front", "outline": [[0,0],[420,0],[420,300],[0,300]],
"quantity": 2, "grade": "B" }
],
"hides": [
{ "id": "H-0412", "outline": [[0,0],[2400,0],[2600,1500],[0,1700]],
"defects": [[[800,600],[850,600],[850,650],[800,650]]] }
],
"sets": 10,
"settings": { "timeLimitS": 300 }
}'A leather job with the outlines sent inline: nothing is stored apart from the job. Full reference.
What your customers get
The rules of each trade, already built in
Not geometry packing for your team to build around: the constraints a leather cutter, a fabric spreader and a panel shop work to, handled by the engine and never traded for yield.
Leather
Hides from scanner files, defects and grade zones, graded sub-zones per part, the fewest hides or the lowest hide cost, complete sets within a batch or shade lot, and the hide of every cut part.
Fabric
The shortest marker on a fixed roll width, stripe and plaid matching, folded and tubular markers with pieces cut on the fold, and orders of thousands of pieces.
Sheets
One sheet size or several, the fewest sheets or the lowest material cost, grain and face rules, and whole kits first when the stock runs short.
True shape nesting
Real outlines with curves and cut-outs, small parts inside the holes of larger ones, rotation, tilt and flip rules per part.
Live progress
Every better nest is reported while the search runs, with its yield, so your interface can show it and your users can stop when it is good enough.
Files ready to cut
One DXF and SVG per hide, sheet or marker with the original layers and curves, part labels on request, and a CSV report per part.
Why a cloud engine
Nothing to ship, nothing to support on customer PCs
No native library
Nothing to compile against, install or keep working on every customer machine and operating system.
Updates reach everyone
When the engine improves, every customer nests with it the same day, with nothing for you to redeploy.
Scales with the order
Big jobs run on cloud machines, not the office PC, and several run side by side: 10 jobs of 60 minutes finish together in 60 minutes, not 10 hours one after another.
More on cloud nesting and why it beats a local engine. Manufacturer connecting your own ERP or warehouse system rather than building a product? See ERP and warehouse integration. Comparing engines? Lescut and NestLib, Lescut and AutoNester.
Questions about the nesting API
What is a nesting API?
A nesting API lets your own software send the parts to cut and the material to cut them from, and get the nest back, without building a nesting engine. Lescut's REST API takes the parts and the hides, roll or sheets over HTTPS, nests them on cloud machines and returns the placements and ready cutting files.
Which materials does it nest?
Leather hides from scanner files, with defects, grade zones, sets, batches and shade lots; fabric on the roll, with stripe and plaid matching and folded or tubular markers; and stock sheets of wood, plastic, composite or metal, on one size or several, at the fewest sheets or the lowest cost, with complete kits first when stock runs short.
Do my customers' patterns have to be stored with you?
No. Your software can send the outlines with each job. No file is stored, the geometry lives only as part of the job, and it is deleted when you delete the job, or about 24 hours after it ends. You can also upload DXF or SVG files once and reuse them as stored libraries.
Can I offer Lescut under my own brand?
Yes. Your customers can use the Lescut app under your brand, so they upload, nest and download without you building the interface. Contact us to set it up.
Can I resell Lescut to my customers?
Yes, on partner terms. An API key acts for one organization and its plan; offering nesting to your own customers, through the API or a branded app, is agreed with us in writing first.
What does the API cost?
The API comes with every Pro and Enterprise plan, from €49 a month, at 60 to 300 requests per minute, and jobs use the plan's engine minutes. You can try it during the 7-day free trial of a Pro plan. Reselling and white label are priced on partner terms.
Is there a nesting SDK, and which languages can call the API?
The API is plain JSON over HTTPS, described in an OpenAPI document, so any language can call it: generate a client for TypeScript, Python, C#, Java or Go, or send requests directly. AI agents and custom GPT actions can load the same document.
How fast does a job return a nest?
A first nest is ready within seconds. The job then keeps improving it until the time limit you set, within your plan's job length; poll the job for the best nest so far, or stop it at any time and keep that nest.
Can the engine run on-premise or offline?
Lescut runs in the cloud by design, because that is where a nest comes out best. Every job gets a dedicated, powerful cloud machine for its whole time limit, and up to 10 jobs run side by side. Offline, nesting shares your customer's office PC or the cutting table's computer, runs one job after another, and is only as good as that machine. An offline engine also falls behind: every improvement waits for your next release and each customer's update, so customers on different versions get different nests. Online there is nothing to install or support, and every customer nests with the latest engine the same day. Your software needs an internet connection to send jobs; if it must nest with none at all, you need an engine library you ship with it.
Does it write toolpaths?
No. Lescut returns placements and DXF and SVG cutting files with your layers; lead-ins, cut order and common-line cutting stay with your CAM or machine software. A cutter profile can rename and recolour layers for each tool.