Previous value: -"What this line costs per unit, in the calculation's currency."New value: +"What this line costs per unit, in the calculation's currency, as shown: a tier adds up exactly to the line above it."

Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "This line's amount before it was rounded for display; a per-lot figure is it times the lot, rounded once."
+}

Previous value: -"The stock the part is bought as — format, size, parts per stock — its mass balance, and the material line's purchase and credits, at the lot the calculation was priced for whichever quantity was asked. Null on a bought-in part and on a calculation priced before 2026-08-28, which recorded no material detail; one priced before the 2026-09-26 release states no scrap or remnant mass and no bar length."New value: +"The stock the part is bought as — format, size, parts per stock — its mass balance, and the material line's purchase and credits, at the lot the calculation was priced for whichever quantity was asked. Null on a catalogue part and on a calculation priced before 2026-08-28, which recorded no material detail; one priced before the 2026-09-26 release states no scrap or remnant mass and no bar length."

Added value: +"uuid"

Previous value: -"How many tiers of cost_lines to return: 1 the cost categories only, 2 (the default) the categories and the tier beneath, null the whole tree. A line cut short states in children_hidden how many lines sit beneath it."New value: +"How many tiers of cost_lines to return: 1 the cost categories only, 2 (the default) the categories and the tier beneath, null the whole tree. A line cut short states in children_hidden how many lines sit beneath it. With a depth set, a line also leaves out the keys it has no value for (null, [] or {})."

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Set on a cost-category row: its key in cost_categories (setup, subcontract, material, machine …), or 'other' on the row that holds every category not listed. Absent on a feature or component row."
+}

Previous value: -"Cost contribution per unit, in the calculation's currency (the result's `currency`) — the DIRECT run-time cost the feature consumes (machine, labour and finishing time), before any setup, programming, tooling or overhead is spread onto it. The tenant's cost-driver card can show the same rows fully loaded, so its per-feature figure is higher than this by one uniform factor; the ranking and the relative shares are identical on both bases."New value: +"Cost contribution per unit, in the calculation's currency (the result's `currency`). On a cost-category row it is that line of the cost sheet. On a feature row it is the DIRECT run-time cost the feature consumes (machine, labour and finishing time), before any setup, programming, tooling or overhead is spread onto it. The tenant's cost-driver card can show the feature rows fully loaded, so its per-feature figure is higher than this by one uniform factor; the ranking and the relative shares are identical on both bases."

Previous value: -"Share of unit cost, 0–100, on the same direct basis as cost. Sum the listed rows against attributed_cost_share_pct, not against 100."New value: +"Share of unit cost, 0–100, on the same basis as cost. The category rows, 'other' included, add up to 100. The feature rows add up to the share the named features explain (attributed_cost_share_pct where the result states it), not to 100."

Previous value: -"1 = the largest driver."New value: +"1 = the largest driver. Cost categories and features are ranked separately; null on the row that holds the categories not listed."

Previous value: -"Unit cost per part at `quantity`: direct cost plus overhead_var and overhead_fixed. Where the costing environment states no Material-/Fertigungsgemeinkosten, overhead_var is the flat variable overhead (platform default 15 % of direct cost); once it states them, that default is 0 and those overheads sit above unit_cost as cost-sheet rungs, with administration and selling, margin and the other surcharges. The price to quote is offer_price."New value: +"Unit cost per part at `quantity`: direct cost plus overhead_var and overhead_fixed. Where the costing environment states no Material-/Fertigungsgemeinkosten, overhead_var is the flat variable overhead the environment states (none by default); once it states them, those overheads sit above unit_cost as cost-sheet rungs, with administration and selling, margin and the other surcharges. The price to quote is offer_price."

Added value: +{
+  "anyOf": [
+    {
+      "minimum": 1,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": 2,
+  "description": "How many tiers of cost_lines to return: 1 the cost categories only, 2 (the default) the categories and the tier beneath, null the whole tree. A line cut short states in children_hidden how many lines sit beneath it."
+}

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "How many lines sit beneath this one that `max_depth` left out: ask again with a larger `max_depth`, or null, to see them. Absent when nothing beneath this line was left out."
+}

Added value: +"Id of a calculation, as upload_and_quote, quote_part or list_calculations return it."

Added value: +"Which tiers to return: 'full' (the default, every tier), 'procurement' (headline and band), 'workprep' (the operations as a work plan), 'operations' (operations and machines) or 'design' (the cost sheet and feature drivers)."

Previous value: -"Adjustable factors that move this line, by name — the keys get_cost_factors publishes and preview_cost accepts. A factor is listed only where this line carries what is needed to work it out, so an empty list does not mean the line is fixed."New value: +"Adjustable factors that move this line, by name: the keys preview_cost accepts. A factor is listed only where this line carries what is needed to work it out, so an empty list does not mean the line is fixed."

Previous value: -"What this step is charged per part at the ordered lot size, in the calculation's currency — set only on an outsourced post-machining step (heat treatment, coating), and part of the subcontract cost line. Null on a machining step: machining cost attributes to features, not to operations (use get_cost_drivers). Null too when the charge was not recorded."New value: +"What this step is charged per part at the ordered lot size, in the calculation's currency — set only on an outsourced post-machining step (heat treatment, coating), and part of the subcontract cost line. Null on a machining step: machining cost attributes to features, not to operations (explain_cost ranks them). Null too when the charge was not recorded."

Previous value: -"One calculation as a single rough-to-detailed hierarchy — headline →\ncost category → operation → feature, with time and cost side by side — so\nevery persona can stop at the depth it needs from the SAME run.\n\n``persona`` selects the slice: 'procurement' (headline + band only),\n'workprep' (the routing / operations tier), 'operations' (routing + machines\nfor balancing), 'design' (cost categories + per-feature drivers), or 'full'\n(every tier). Tiers not relevant to the persona come back empty.\n\nThe category tier is the itemised cost sheet: ``cost_lines`` is the whole\ntree — cost category, then per machine, per clamping, per work element —\nand ``cost_categories`` is its top level flattened for a quick read. Both\ncome from the one sheet the cost-sheet endpoint serves and the app renders,\nso an agent and a person read the same numbers rather than two\nderivations of them. This is the CATEGORY axis of the cost; for the\nFEATURE axis (which pocket, which hole) use get_cost_drivers."New value: +"One calculation as a single rough-to-detailed hierarchy — headline →\ncost category → operation → feature, with time and cost side by side — so\nevery persona can stop at the depth it needs from the SAME run.\n\n``persona`` selects the slice: 'procurement' (headline + band only),\n'workprep' (the routing / operations tier), 'operations' (routing + machines\nfor balancing), 'design' (cost categories + per-feature drivers), or 'full'\n(every tier). Tiers not relevant to the persona come back empty.\n\nThe category tier is the itemised cost sheet: ``cost_lines`` is the whole\ntree — cost category, then per machine, per clamping, per work element —\nand ``cost_categories`` is its top level flattened for a quick read. Both\ncome from the one sheet the cost-sheet endpoint serves and the app renders,\nso an agent and a person read the same numbers rather than two\nderivations of them. This is the CATEGORY axis of the cost; for the\nFEATURE axis (which pocket, which hole) explain_cost ranks the drivers."

Previous value: -"The costing environment this was priced in. get_cost_factors takes it and reads the factors named in each line's ``factors``, their range and where each one is saved."New value: +"The costing environment this was priced in: the machines, rates and overheads the factors named in each line's ``factors`` belong to."

Previous value: -"The costing environment this was priced in — pass it to get_cost_factors to read the factors named in each line's ``factors``, their range and where each one is saved."New value: +"The costing environment this was priced in. get_cost_factors takes it and reads the factors named in each line's ``factors``, their range and where each one is saved."

Previous value: -"Quote-trust headline — is this number calibrated to the shop, or a model\nestimate? The signal a procurement / supplier persona reads alongside the\nprediction band before trusting a should-cost."New value: +"Quote-trust headline — is this number calibrated to the shop, or a model\nestimate? The signal a procurement / supplier persona reads alongside the\nprediction band."

Previous value: -"Quote-trust signal — the headline the procurement / supplier persona reads with the band before trusting the should-cost."New value: +"Quote-trust signal — the headline the procurement / supplier persona reads together with the prediction band."