Precursor embedded-emissions aggregation incl. the 2028 scrap rule (ART-72) -> consignment embedded-emissions calculation (ART-69) -> Merkle integrity over the supplier data set (cry-04). Lets a complex-goods producer supply verifiable embedded emissions to its importer; pre-positions the downstream-180 scope extension.
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
}
verify_merkle_batch{
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"name": "verify_merkle_batch",
"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: No precursor data was supplied for these complex goods. What does the roll-up compute once one precursor is declared?
Run the AINumbers MCP tool `run_chain` with {"chain":"cbam-precursor"} and read `art-72-cbam-precursor-emissions-aggregator.cumulative_see_tco2e`.
Re-run with `inputs` for `art-72-cbam-precursor-emissions-aggregator`, reusing the values that result echoed, with `precursors` changed so one precursor at mass_fraction 0.6 with see_tco2e_per_t 2.1. 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.html