CVP verified calculation capability

Energy cost Calculation Capability

Estimate electricity cost from watts/hours or kWh and a unit rate.

Electrical Capability ID electrical.energy_cost version 1.4.2 CVP VERIFIED CURRENT Engineering

Model

Cost from energy

Cost from energy: Cost = kWh × rate
Cost from watts: Cost = (W × h × days ÷ 1000) × rate
Daily cost: Cost/day = (W × h/day ÷ 1000) × rate
Energy and power: E = P × t · P = E / t

Modes: watts · kwh

Inputs / Outputs

Canonical symbols for this capability. Agent schemas remain the contract.

Symbol	Quantity	Unit	Role
`W`	Power	—	input
`hours`	Hours per day	—	input
`days`	Number of days in the billing period	—	input
`rate`	Unit rate	—	input / output
`kWh`	Energy	—	input
`api_version`	—	—	output
`api_contract_version`	—	—	output
`spec_version`	—	—	output
`page`	Canonical calculator page URL	—	output
`links`	—	—	output

Assumptions / Validity

Declared scope for this capability. Do not use it outside this domain.

Assumptions

Constant average power over the period
Single flat unit rate

Example

One numerical check. The calculator page holds worked steps and FAQ.

1000 W × 4 h/day × 30 days × $0.15/kWh = $18

Open this example in the calculator

Trust

CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance. Computational verification is defined by CVP. Supplemental domain review (internal) and named expert review are defined by the Review policy and do not by themselves determine CVP conformance.

CVP: CVP VERIFIED · CVP protocol 1.0.0-proposed · Engineering assurance· View Manifest · CVP overview · Specification
Assurance: Engineering
Declared partition coverage: PASS · 3/3 declared partitions (watts, kwh, invalid-domain)
Calculation version: 1.4.2
Verification: 28/28 calculation tests · 10/10 legacy golden · 13/13 legacy boundary · 5/5 legacy property
Production surface contract: 6/6
Versions: Calculation 1.4.2 · CVP protocol 1.0.0-proposed · Evidence 2026-09-13.ssr-dollar-literal
Verification revision: 2026-09-13.ssr-dollar-literal · 5/5 property · digest b2d8bb7116f1
Reference: O1 model · O2 expected_values · O2 numerical_behavior
Interfaces: PASS · UI (SSR) / REST / MCP
ui-ssr is query-result HTML, not a live browser session. Public share URLs use UI ids (powerInput/hoursInput/daysInput/kwhInput/rateInput). CVP-IFACE includes those serialized queries, not only canonical engine keys.
CVP suite: 2/2 golden · 12/12 CVP boundary · 21/21 invalid · 5/5 property · 3/3 cross-interface · 4/4 CVP contract
Supplemental domain review: Internal · Pass · electrical-engineer
Named expert review: Not performed
Version lock: Supported (409 VERSION_MISMATCH)
Artifact consistency: Build verified · 1.4.2 (workspace artifacts agree)
Review-policy tier: Internally reviewed — catalog token internally_reviewed; supplemental; not CVP status

This calculator CURRENT · Public schema 1.4.2 matches · Semantic contract ✓ · Production attested · Public/cache ✓ · Origin ✓

Call this capability

Human page, REST, and MCP share the same engine and calculation_version. Build verified hashes workspace artifacts only. After deploy, attest:production GETs canonical URLs twice — the public/cached view an Agent actually hits, and origin — including every /capabilities/{id} HTML page. Public Capability HTML version must match catalog before production attestation passes. Live Trust rows above fetch /.well-known/calculatorx-production-attestation.json and the output schema const. Build hashes: release integrity. That proves currently published page / engine / schema / evidence / MCP agree — not that a historical version is independently immutable. Reference Calculation Standard — Production surface contract 6/6.

curl -sS -X POST 'https://www.calculatorx.com/api/v1/calc/energy-cost' \
  -H 'Content-Type: application/json' \
  -d '{"inputs":{"mode":"watts","W":1000,"hours":4,"days":30,"rate":0.15},"calculation_version":"1.4.2"}'

{
  "inputs": {
    "mode": "watts",
    "W": 1000,
    "hours": 4,
    "days": 30,
    "rate": 0.15
  },
  "calculation_version": "1.4.2"
}

POST /api/v1/calc/energy-cost. This is a POST calculate endpoint — do not GET it.

Full REST contract: REST API docs.

Tool id: energy-cost
Engine: energy-cost
REST: POST /api/v1/calc/energy-cost
MCP: execute_calculation with capability_id: "electrical.energy_cost"
Agent input schema: Canonical (MCP / Agent)
Output schema: JSON Schema (latest)
Versioned input schema: Immutable pin (1.4.2)
Versioned output schema: Immutable pin (1.4.2)

Operations

Declared calculation modes for this capability.

watts
kwh

References

Human-readable sources plus CVP reference evidence classes.

Sources

Reference evidence classes: O1 model · O2 expected_values · O2 numerical_behavior

Try with an agent

Inspect, then execute. Same engine as REST and the human calculator.

curl -sS -X POST 'https://www.calculatorx.com/mcp' \
  -H 'Content-Type: application/json' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/call' \
  -H 'Mcp-Name: inspect_capability' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"inspect_capability","arguments":{"capability_id":"electrical.energy_cost"},"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientInfo":{"name":"calculatorx-docs-example","version":"1.0.0"},"io.modelcontextprotocol/clientCapabilities":{}}}}'

curl -sS -X POST 'https://www.calculatorx.com/mcp' \
  -H 'Content-Type: application/json' \
  -H 'MCP-Protocol-Version: 2026-07-28' \
  -H 'Mcp-Method: tools/call' \
  -H 'Mcp-Name: execute_calculation' \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"execute_calculation","arguments":{"capability_id":"electrical.energy_cost","inputs":{"mode":"watts","W":1000,"hours":4,"days":30,"rate":0.15},"calculation_version":"1.4.2"},"_meta":{"io.modelcontextprotocol/protocolVersion":"2026-07-28","io.modelcontextprotocol/clientInfo":{"name":"calculatorx-docs-example","version":"1.0.0"},"io.modelcontextprotocol/clientCapabilities":{}}}}'

Pin calculation_version (1.4.2) when the result must stay reproducible.

Inspect the trust tier and required assurance level before execution. Full protocol notes: MCP docs.