The Day QIO: optimisation you can verify and own
One engine sits under a subset of our engagements: the Day QIO (Quantum-Inspired Optimization) API, sold on its own terms to companies who build optimisation work for other people. Two things are worth spelling out plainly: what it does, and who it is sold to.
What the optimisation API does
Most problems worth optimising — routing, scheduling, allocation, assignment — reduce cleanly to an Ising model or a QUBO (quadratic unconstrained binary optimization) formulation, and this API solves them in that form.
What you get
- One interface. A single, unified QUBO matrix is the input across every backend — classical today, on ordinary processors; quantum-hardware runs are registered and not run — so the call you write does not change when the engine underneath it does.
- A ground truth you can check. At 20 variables or fewer, the exact, verifiable global optimum is always available — not a heuristic's best guess with no stated distance from the answer.
- You own the implementation we write for you, under the licence the engagement names; our pre-existing tools stay ours. An engagement leaves you holding the implementation, not a subscription to someone else's closed solver.
- An engagement, not a commodity subscription. Delivered as a client consulting relationship, scoped and reasoned about like the rest of our work — not a metered API you self-serve and hope fits.
- A quantum path, stated plainly. Classical solvers win today, so that is what we run. The engine is classical today, on ordinary processors; quantum-hardware runs are registered and not run.
The API for professionals who build on optimisation
The Day QIO API is not sold to individuals or end-users. It is sold to development and consulting companies — people building or delivering optimisation work for someone else — under a written agreement with Agile Integrations LLC; for calls on your own key, embark.day sells prepaid credit.
Every problem you bring is formulated as a QUBO and dispatched to whichever solver tier fits its scale and latency — picked for the problem, not something you have to choose yourself.
The engagements this engine runs for clients, and the environmental-sensing engagement, are on the services page. This page is the API itself.
Beyond the solver: build and own the model
Everything above runs a solver on a problem you formulate. The professional API is the next step up: a tier that builds and composes the models themselves — you bring the pieces or the data and get back a single model you own outright, with a certificate you can re-check yourself. Same engine, same invoice-only footing; a different kind of work.
Where this starts
A short technical conversation, not a sales call: tell us the problem you want formulated, and we will tell you which solver tier it needs and what building it would cost.