W-A flagship. Embedded-emissions calculation (ART-69) -> default-value resolution (ART-70) -> certificate cost + free-allocation phase-out + holding/surrender schedule (ART-71). The importer-to-customs CBAM declaration lifecycle end-to-end. Decision-support draft, not a filed declaration.
resolve_cbam_default_value{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "resolve_cbam_default_value",
"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
}
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: We import iron and steel on default emissions values while paying a carbon price at origin. What CBAM certificate cost follows?
Run the AINumbers MCP tool `run_chain` with {"chain":"cbam-liability"} and read `art-71-cbam-certificate-cost-engine.certificate_liability_eur`.
Re-run with `inputs` for `art-71-cbam-certificate-cost-engine`, reusing the values that result echoed, with `origin_carbon_price_eur_per_t` changed so no origin carbon price applies, so it is 0. 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-liability.html