The calco2la.to connector libraries are an early proof of concept for integrating emission calculation APIs through a stable, provider-neutral abstraction layer.
Instead of binding a specialist application directly to one calculation provider, the connector approach separates application logic from provider-specific request and response formats. The goal is to make CO₂ calculation more testable, replaceable and governable over time.
Proof of concept
The public repositories show the architectural direction and first implementation work. The newest general scheme.json and providers.xml work discussed internally is not fully pushed yet.
The connector approach is meant for organizations and software projects that need more than a one-off calculator call.
A connector layer turns provider-specific APIs into a governable integration boundary.
Applications should not have to know every provider-specific API detail. A connector layer makes switching, testing and comparing providers easier.
Provider choice, calculation policy and supported features should remain transparent and configurable rather than disappearing into custom code.
The same domain request can be mapped to different providers, making side-by-side testing and migration paths possible.
calco2la.to is designed around repeatable, transparent calculation responses that include the parameters needed to understand and document a result.
The repositories show the connector direction. Java is currently the working example; Python and PHP are prepared as implementation targets.
Even in proof-of-concept state, the architectural target is clear enough to guide implementation and evaluation.
The public repositories are intentionally transparent about the current proof-of-concept state.
The shared request and response schema is being refined so that providers can be described and mapped consistently across languages.
The providers.xml concept is intended to describe provider-specific endpoints, capabilities and mappings without hardcoding every provider into application logic.
The Java implementation currently acts as the working example. Python and PHP are planned to follow the same structure once the shared schema and provider metadata stabilize.
The long-term goal is to support multiple emission calculation providers through the same domain model, allowing tests, comparisons and controlled migration paths.
The connector layer creates a stable boundary between specialist applications and provider-specific APIs.
We can help evaluate whether the connector approach fits your system landscape, provider strategy and governance requirements.
