calco2la.to
Public-sector CO₂ calculation infrastructure

Pricing for API, connector, governance and integration support

Start with open web access, evaluate the API and connector approach in a pilot, and scale towards organization-wide or framework-level deployment.

From public access to framework deployment

Packages

The free tiers help users understand the system. The paid packages make CO₂ calculation usable in real administrative and software processes.

Open

Open Access

FREE

No login required

For occasional public use and demonstration of the web calculator.

  • Web calculation without account
  • Heavy rate limiting
  • No exports, no saved history, no logs
  • Connector libraries remain freely inspectable
Registered

Registered Account

FREE

For testing workflows

For users who want saved examples, exports and a less restricted web experience before integration.

  • Calculation history
  • Basic exports
  • Less restrictive web rate limits
  • Documentation and connector access
Organization

Organization License

from
€12,000 / year

For institutional integration

For institutions integrating CO₂ calculation into internal systems and administrative workflows.

  • Multiple API keys
  • Organization-level API key management
  • Sub-organizations and key ownership
  • Higher fair-use request volume
  • Integration support allowance
Framework

Framework / State-Level License

Custom

For multi-organization deployment

For ministries, umbrella organizations, shared services, or state-level rollouts.

  • Full organization tree
  • User and role management
  • Many or contractually unlimited API keys
  • Contractually defined high-volume use
  • Custom SLA and rollout support
Capabilities

Comparison

The tiers are organized around practical use: web calculation, API access, connector integration, governance, auditability and support.

Capability Open Access Registered Account Pilot / Evaluation Organization License Framework License
Web calculation
Web calculator Included Included Included Included Included
Saved history No Basic history Pilot history Organization history Configurable
Exports No Basic exports Pilot exports Administrative exports Custom
API access
Production API key No No 1 production key Multiple keys Many or contractually unlimited keys
Test API key No No 1 test key Included Included
Request volume Rate limiting Moderate limits Capped volume Generous fair use Contractual high-volume model
Connector and integration
Connector libraries Included Included Included Included Included
Integration review No No Basic review Included allowance Custom rollout support
Vendor-neutral integration strategy Documentation only Documentation only Pilot guidance Included Strategic rollout support
Organization and governance
Organization model No Personal account One organization Organization with sub-units Full organization tree
User and role management No No Limited Included Included
API key ownership No No Simple Included Included
Auditability and replayability
Replayable API responses No API access No API access Included Included Included
Versioned API behavior No API access No API access Pilot version Stable versioning Contractual versioning model
Long-term verification options No No On request Available Custom
Support
Support channel No individual support No individual support Email support Email and integration support Custom support model
Procurement and rollout support No No Pilot documentation Available Included

Why not price only by API calls?

For public-sector use, the main value is not only the calculation endpoint. The package includes integration help, sensible software architecture, governance, auditability, replayability, API-key management, and a clear path from pilot to organizational rollout.

Request volumes should be predictable and fair, but they should not become the main design principle for administrative infrastructure.

FAQ

Frequently asked questions

Short answers for evaluation, procurement and rollout planning.

Choose a pilot if you are still testing the API, connector model, data flow, or organizational fit. Choose an organization license once one or more systems should use the service in regular operation.

Yes. The connector approach is meant to avoid binding a specialist application directly to one provider-specific API. Vendors and internal IT teams can integrate against a stable domain interface.

Free and pilot usage is limited. Organization licenses include generous fair-use volumes. Framework licenses can define high-volume or unlimited usage contractually, depending on deployment and support requirements.

Yes. Pilot packages, organization licenses, framework agreements, and integration support can be structured to fit procurement, rollout, and governance requirements.

Not sure which package fits?

Tell us whether you are evaluating the API, integrating a specialist system, or planning an organization-wide rollout. We can help map the right package and next steps.