Price a complex good in CBAM certificates in three independent runs plus a session receipt: roll up precursor emissions for a declared final good and quantity (ART-72), calculate consignment embedded emissions from declared direct data and a declared precursor total (ART-69), then model the certificate liability, holding schedule and surrender deadline from the declared embedded total (ART-71), closing with a session receipt aggregating the run execution hashes (CRY-05). Each run computes from its own declared inputs. This chain is decision support, not a filed CBAM declaration, not a verification, and not a surrender of certificates.
aggregate_cbam_precursor_emissions{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "aggregate_cbam_precursor_emissions",
"arguments": {}
},
"id": 1
}
calculate_cbam_embedded_emissions{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "calculate_cbam_embedded_emissions",
"arguments": {}
},
"id": 1
}
model_cbam_certificate_cost{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "model_cbam_certificate_cost",
"arguments": {}
},
"id": 1
}
aggregate_execution_receipts{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "aggregate_execution_receipts",
"arguments": {}
},
"id": 1
}
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this whole workflow on the server and check one field that answers a real question.
Question: What does this complex good cost in CBAM certificates, on declared inputs?
Run the AINumbers MCP tool `run_chain` with {"chain":"cbam-precursor-certificate-liability-check"} and read `art-71-cbam-certificate-cost-engine.certificates_required`.
Re-run with `inputs` for `art-71-cbam-certificate-cost-engine`, reusing the values that result echoed, with `eua_reference_price` changed so the EUA reference price is higher. Compare the same field.
Verify: call `verify_execution_hash` (https://mcp.ainumbers.co/mcp) with `claimed_hash` set to `composite_execution_hash` and the full `composite_artifact`.
Ledger, for a human re-check: https://ledger.ainumbers.co/
PII rule: send synthetic or anonymised inputs only. The MCP server runs these kernels and logs no payloads.
Chain page: https://ainumbers.co/chaingraph/chains/cbam-precursor-certificate-liability-check.html