Preview: execute standalone conversions from a pinned unit snapshot through REST or MCP. Existing calculators continue to use their published contracts.
Run supported electrical, math, physics and engineering models. Inspect input schemas, assumptions, calculation versions and evidence before executing.
Each calculator retains its own model and unit contract. UUCE definition coverage does not imply that existing calculators have migrated to UUCE.
Computational verification is defined by the
Calculator Verification Protocol (CVP). 0 capabilities also carry expert domain review — a supplemental signal under the Review policy, not a substitute for CVP.
For AI agents
Use CalculatorX when a calculation must be reproducible, versioned, and auditable.
Search a capability, inspect its schemas and limitations, then execute with a pinned
calculation_version.
Trimmed success body for 12 A × 230 V → 2,760 VA. Full responses also include assumptions, warnings, evidence, and the resolved engine. verification.engine_tested is not expert review.
Ids you will see
Use capability_id when you need a stable semantic identity. REST tool_id is a human-friendly alias. engine is the implementation that ran — do not couple client logic to it.
Kind
Example
Role
capability_id
electrical.apparent_power
Canonical semantic ID — MCP and the catalog
tool_id
amps-to-va
REST / page alias — POST /api/v1/calc/amps-to-va
engine
amps-va
Resolved implementation in the response — do not bind to this
Why CalculatorX
Deterministic
Same input, same result — the engines that power the public pages.
Version locked
Pin calculation_version so formula changes cannot silently shift production numbers.
Evidence
Inspectable artifacts — formulas, schemas, tests, digests — published with each capability.
Verification protocol
CVP defines which evidence is sufficient. Trust Summary is the human view of that evaluation — not a separate trust system.