CalculatorX Developers
Versioning & verification
214 templated capabilities. 214 are engine-tested or higher. Verification status is defined under CVP.
CalculatorX calculations are deterministic, versioned, and checkable. Pin a version when you need the same formula tomorrow. Freeze a result with snapshots; failed calls are documented under Errors.
Verification status for a calculator is determined under the Calculator Verification Protocol (CVP). Evidence catalogs show what was recorded; CVP defines whether that evidence is sufficient.
Version lock
Pin a published calculation version so agents do not silently pick up formula changes:
curl -sS -X POST 'https://www.calculatorx.com/api/v1/calc/amps-to-va' \
-H 'Content-Type: application/json' \
-H 'CalculatorX-Spec-Version: 1.4.3' \
-d '{"inputs":{"mode":"amps-va","primary":12,"volts":230,"phase":"single"}}'
You may also send calculation_version in the JSON body. Mismatch returns HTTP 409 with code: "VERSION_MISMATCH".
| Field | Meaning |
|---|---|
api_version |
HTTP API surface (v1) |
api_contract_version |
Shared response/engine contract (bump on breaking API shape changes) |
calculation_version / spec_version |
This tool's calculation version (matches the on-page Spec) |
| CVP version | Protocol revision used for verification (see CVP) |
| Verification suite version | Vectors, properties, coverage partitions for a CVP run |
| Attestation status | Production binding: CURRENT / STALE / … |
Evidence & CVP
Each templated capability publishes input/output schemas, test counts, limitations, and artifact digests.
| Path | Role |
|---|---|
| /developers/cvp | Protocol overview — what “verified” means |
| /developers/cvp/spec/1.0 | Normative CVP 1.0 specification |
| /evidence/ | Verification evidence UI + JSON |
| /capabilities/ | Capability catalog (tier, schemas, MCP/REST) |
| /.well-known/calculatorx-capabilities.json | Machine catalog |
| /openapi.json | OpenAPI 3.1 for core capabilities |
| /schemas/ | JSON Schema 2020-12 input/output per capability |
| /.well-known/calculatorx-spec-registry.json | Pages ↔ engines ↔ embed ↔ API paths |
| /.well-known/agent-tools.json | HTTP tool descriptions |
| /.well-known/llms.txt | Short agent-oriented site summary |
| /for-agents | Canonical agent usage contract |
Review policy (supplemental)
Human / domain review tiers (engine_tested, expert_verified, …) are defined on the Review policy page. Prefer CVP Verified + CURRENT attestation for production agent use; Review-policy tiers are supplemental filters. Catalog token verified is L3 only (expert_verified).
Domain Expert Review is a supplemental assurance signal. It does not by itself determine CVP conformance.