Live API
Send a plain-English shipment description. Receive the containers used, utilisation, unpacked items, optional x/y/z placements and a link to the interactive 3D result.
Packing optimisation infrastructure
Add 3D load planning to your product—without building a packing solver
Use the live packing API and interactive 3D planner, then connect one real workflow through a fixed-scope founding pilot.
Start with ten historical loads and one anonymised payload. Engineering begins only after the fit is clear.
Three ways to put the solver to work
Start self-serve, embed the working planner, or scope one production integration with the founder.
Embeddable planner
Put the working planner inside a portal or internal tool with an iframe. Saved plans remain shareable with the people who load the vehicle.
Fixed-scope implementation
Map one existing WMS, TMS, ERP or spreadsheet workflow to the solver, with boundaries and success criteria agreed before work starts.
The product is live
Mixed SKUs, quantity limits, stacking, orientation, weight, loading order, multiple containers, Excel export, print and a shareable 3D plan are already working in the planner below.
This is the real application, not a mock-up. Open it, enter a representative load and inspect the result before discussing a pilot.
What the public API returns today
POST /api/ai/calculate accepts a natural-language prompt of up to 4,000 characters plus credentials and an optional speed. It returns container summaries, unpacked items, free-space pockets and a shareable 3D plan. Add ?coordinates=true to receive every packed item's name, packed dimensions and x/y/z position.
Need deterministic typed item rows, stable source-system IDs, an explicit loading sequence or a white-label viewer? Bring a representative anonymised payload and the fields your system must receive. Those requirements are validated and scoped before they become a contract—we do not ask you to integrate against a guessed schema.
From sample data to one production workflow
The pilot is deliberately small enough to prove value without turning into an open-ended software project.
-
Send one anonymised payload
Share the item rows, container choices, operational constraints and the result your system needs back. No production credentials are required for scoping.
-
Replay ten historical loads
Compare the plans against what your team actually shipped: containers used, utilisation, time spent and any load that operations would reject.
-
Agree one workflow and one contract
Choose the single trigger, payload and result that matter first. Document authentication, errors, limits and ownership before implementation.
-
Ship, measure and decide
Put that workflow in front of real users, measure adoption and operational value, then expand only if the evidence supports it.
Founding integration pilot
For the first three partners who have a real payload, an internal owner and a workflow they can put in front of users.
$750/month for 3 months
- The live API and commercial embedding rights for the agreed pilot workflow
- One bounded integration or data-mapping workflow
- Up to eight founder engineering hours across the pilot
- Direct technical support and a written integration contract
- A go/no-go review against agreed adoption and value measures
Bounded on purpose
The monthly price proves recurring demand. It does not buy an unlimited custom-development queue.
- New solver capabilities and open-ended data cleanup are quoted separately
- On-premise deployment, custom SLA and security work are scoped before commitment
- Additional workflows start only after the first one is used in production
A good fit
The pilot is designed for a team whose packing problem repeats and can be measured.
- A WMS, TMS, ERP or logistics platform adding load-planning capability
- A manufacturer, distributor, exporter, 3PL or forwarder planning recurring mixed loads
- A team with historical loads and someone who owns the workflow
- A buyer willing to pay for a production test, not only a demo
Use the planner instead
If you pack occasionally, do not need the result inside another system, or cannot test against historical loads, the self-serve planner is the simpler product.
Open the plannerIntegration questions
Is there a working API today?
Yes. The public endpoint accepts a natural-language shipment description and returns container summaries, unpacked items, optional placements and a link to the 3D plan. The API docs include live demo credentials.
Does the public API accept structured item rows?
Not as its public contract today. The application itself already works with structured items. A pilot validates the exact request and response fields your system needs before a typed external contract is built.
Do you return every box coordinate?
Yes. Add ?coordinates=true and each container includes an items array with every item's name, packed length, width and height, and x/y/z position. Stable source-system IDs and an explicit loading sequence are not part of the public contract today.
Can we embed the 3D result?
Yes. The planner has an iframe mode, and saved plans open through shareable links. Attribution, branding and commercial use for your workflow are agreed in the pilot.
What happens after three months?
If the workflow is used and creates measurable value, we agree the ongoing API volume, support and any next integration. If it does not, the pilot ends without turning into an indefinite consulting project.
Bring one real payload
Tell us what system it comes from, what result must go back and who will use it. We will answer with a fit check and a bounded pilot scope.
Discuss an integration