Question 1

Which scopes are covered?

Accepted Answer

All three: Scope 1 (fuels, company vehicles, refrigerants), Scope 2 (grid electricity by region, district heat — location-based), Scope 3 (flights incl. radiative forcing, rail, hotels, freight, spend-based categories, waste, water, remote work, commuting).

Question 2

Where do the emission factors come from?

Accepted Answer

A curated built-in library of ~36 indicative factors derived from DEFRA/EPA/IEA-style datasets (2024 values), region-aware where it matters. You can add custom factors that override the library. Verify factors before regulatory filings.

Question 3

How does the API work?

Accepted Answer

Create a key in the console, then POST activities (single or batches up to 100) to /api/v1/carbon/activities with Bearer auth — the response includes computed CO2e per item. GET /footprint returns scope/category totals for any period. Requests are metered.

Question 4

Can it do spend-based Scope 3?

Accepted Answer

Yes — spend-based factors (kgCO2e per USD) for cloud/IT, professional services, construction, catering, office supplies, furniture, telecoms, and financial services. Log the spend, get the estimate.

Question 5

Is this audit-ready?

Accepted Answer

It's structured and auditable (every activity stores its factor and computation), which is what auditors want to see — but the factors are indicative, so confirm them against current national datasets before an audited or regulatory filing.

Question 6

Market-based Scope 2?

Accepted Answer

Yes — dual reporting per the GHG Protocol. Set your supplier-specific electricity factor in the agent's configuration (0 for a 100% renewable tariff with certificates) and every footprint and report shows Scope 2 both location-based (grid averages) and market-based.

Carbon Accounting API

What it does

Key outcomes

Who it's for

Use cases