The rectifier, the controller and the transform - computed, not sketched.
The verified recipe corpus was written for this work: rectifiers, buck converters, transistor amplifiers, PD controllers, friction models, Poincaré sections, field plots and streamlines. Engineering problems are parametric - a model and its constants - which is exactly the shape Qurak computes from.
It computes from your model, not from your files: Qurak solves what you write down, and does not read spreadsheets or datasets.
It computes from your model, not from your files: no Import, no instrument dumps, no CSVs. Derive the response, sweep the parameter, plot the field - and keep the data pipeline where it lives today.
Every example here was run by the engine that will run yours.
| You write | It answers |
|---|---|
| DSolve[{v'[t] == -v[t]/(r c), v[0] == v0}, v[t], t] | {{v[t] -> v0/E^(t/(c*r))}} |
| LaplaceTransform[Sin[3 t], t, s] | 3/(9 + s^2) |
| FourierTransform[Exp[-t^2], t, w] | 1/(Sqrt[2]*E^(w^2/4)) |
Plot[Exp[-x/5] Sin[2 x], {x, 0, 10}] · Plots render as SVG, in the workbench and over the API.Qurak is an MCP server, so Claude, Cursor, VS Code and any other MCP client can hand it a calculation and get a real answer back instead of a plausible one. There is an HTTP API for everything else. Both are open on the free plan.
A paid account raises the budget to 15 seconds per evaluation - the difference between an answer and a timeout on a real model.