canonical: https://jentic.com/apis/greencalculus.com/greencalculus

# GreenCalculus API

The GreenCalculus API resolves sourced greenhouse-gas emission factors and turns activity data into audit-traced carbon calculations, each value returned with its exact source reference and data version. Calculation endpoints cover activity emissions, EN 15978 embodied carbon, PCAF Part A financed emissions, Scope 2 electricity, freight, spend-based, and business travel, with a batch endpoint for mixed methodologies. It also exposes a factor corpus, coverage, a change feed, and a per-account watch list for tracking factor updates.

## For AI agents

Lets an AI agent resolve sourced emission factors and compute audit-traced greenhouse-gas emissions across several methodologies, each with provenance.

## Scope

Does not handle carbon offset purchasing, utility billing, or ESG report filing. Use for sourced emission factors and greenhouse-gas calculations only.

## Capabilities

- Resolve a greenhouse-gas emission factor by canonical key with full provenance
- Convert activity data into emissions with unit conversion and working shown
- Calculate whole-life embodied carbon under EN 15978
- Compute PCAF Part A financed emissions with an audit trail
- Report Scope 2 electricity emissions with location and market methods
- Watch factor keys and read what changed between data releases

## Use cases

### Agent-run carbon accounting

An AI agent can compute an organization's emissions through GreenCalculus by resolving the right emission factor, converting activity data into emissions with the working shown, and citing the exact source reference and data version for each value. Because every result carries provenance, the agent's output is auditable. Connected through Jentic, the agent calls only the calculation and lookup operations it needs.

Example prompt: Resolve the emission factor for an activity, calculate its emissions with unit conversion, and return the source reference and data version

### Financed and embodied emissions

Sustainability teams need methodology-specific calculations they can defend in an audit. GreenCalculus computes PCAF Part A financed emissions with an attribution audit trail and whole-life embodied carbon under EN 15978, each boundary-aware. An agent can run these for a portfolio or a building and keep the audit trail attached.

Example prompt: Compute PCAF Part A financed emissions for a holding and return the attribution and audit trail

### Factor change tracking

Emission factors are revised between data releases, and a reported number can drift out of date. GreenCalculus exposes a change feed and a per-account watch list, so an agent can watch the factor keys a report depends on and read exactly what each release changed. The coverage endpoint shows which countries hold data.

Example prompt: Watch a factor key and read what changed for it between two data release dates

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/factors/{key}` | Resolve one factor by canonical key |
| GET | `/v1/factors` | Browse or search the factor corpus |
| POST | `/v1/calculate/ghg-activity` | Convert an activity into emissions |
| POST | `/v1/calculate/embodied` | Calculate whole-life embodied carbon |
| POST | `/v1/calculate/pcaf` | Compute PCAF Part A financed emissions |
| POST | `/v1/calculate/batch` | Run up to 100 mixed-methodology calculations |
| GET | `/v1/changes` | Read the change feed across data releases |

## Key resources

- **Factors** — Resolve and browse sourced emission factors with provenance and history
- **Calculations** — Activity, embodied, PCAF, electricity, freight, spend-based, and travel emissions
- **Changes** — Change feed and per-release detail of what each data release altered
- **Watch list** — Per-account watched factor keys, diffs, and digest cadence
- **Coverage** — Which countries the corpus holds data for

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 50 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 66 / 100
  - AI-Readiness & Agent Experience: 24 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 74 / 100
- **View full report:** https://jentic.com/apis/greencalculus.com/greencalculus/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring GreenCalculus by hand means handling its Bearer key, picking the right calculation endpoint per methodology, and threading the data version through each result yourself. Through Jentic you install once, import GreenCalculus from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** GreenCalculus carries activity inputs and factor keys in the path and body, so a rule bounds which operations your agent may call rather than which factor. You choose the operations it may call, so the watch-list operations are not included unless you add them.
- **Credential handling:** Your GreenCalculus key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'calculate activity emissions' or 'resolve an emission factor', and Jentic returns the matching GreenCalculus operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **CarbonAPI** — Carbon footprint calculation versus GreenCalculus's sourced-factor, audit-traced results.
- **South Pole Emissions API** — Another emissions-calculation provider versus GreenCalculus's methodology coverage.
- **Cloverly Carbon Offset API** — Buy carbon offsets after GreenCalculus computes the footprint.

## FAQ

### What authentication does the GreenCalculus API use?

GreenCalculus authenticates with your API key as a Bearer token in the Authorization header, per its OpenAPI spec. Several public endpoints, such as health, factor browse, coverage, and the change feed, need no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.

### Can I calculate emissions with provenance using the GreenCalculus API?

Yes. The activity calculation returns emissions with unit conversion and the working shown, and every value comes back with its exact source reference and data version. Methodology-specific endpoints cover embodied carbon under EN 15978, PCAF Part A financed emissions, and Scope 2 electricity.

### What are the rate limits for the GreenCalculus API?

The OpenAPI spec does not publish fixed per-second rate limits, and the batch endpoint accepts up to 100 mixed-methodology calculations in one call. Check https://greencalculus.com/developers/ for current limits.

### How do I calculate activity emissions with the GreenCalculus API through Jentic?

Search Jentic for 'calculate activity emissions' and it returns the GreenCalculus activity-calculation operation with its input schema, so your agent fills the body and calls it. Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import GreenCalculus from the API Directory, and store your key once. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with GreenCalculus?

Yes. Write a rule that allows only the calculation and factor-lookup operations, so the agent can compute emissions and resolve factors but cannot change your watch list, and every call it makes is logged.

### Is there a GreenCalculus MCP server?

You don't need an MCP server to connect your agent to GreenCalculus. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers and calls the operations it needs on demand.