Emitwise

Emitwise is a London-based carbon accounting and Scope 3 reporting platform that uses AI to help large enterprises measure, manage, and reduce their product carbon footprint (PCF) and supply-chain greenhouse-gas emissions. The platform ingests spend data, activity data, and supplier information, auto-classifies suppliers, and produces audit-ready emissions reporting aligned with the GHG Protocol (Scope 1, 2, and 3) and frameworks such as CDP and CSRD. The Emitwise developer API at api.emitwise.com exposes facilities, projects, activity-data files, schema metadata, and aggregated supplier emissions data so customers can integrate carbon accounting into procurement, ERP, and sustainability reporting systems. Access is granted per-customer through Emitwise CSMs; API keys are generated from the Company settings area of the dashboard. In July 2025, Emitwise was acquired by Green Project Technologies; the Emitwise platform and team are now part of Green Project's end-to-end decarbonization solutions, while the existing Emitwise developer portal and API endpoints remain live for customers.

Emitwise publishes 5 API contracts indexed on the APIs.io network, including Facilities API, Files API, Projects API, and 2 more. Tagged areas include Carbon Accounting, Greenhouse Gas, Scope 3, Supply Chain Emissions, and Product Carbon Footprint.

The Emitwise catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

Emitwise’s developer surface includes authentication, documentation, privacy policy, engineering blog, GitHub presence, and 10 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

33.0/100 thin ▬ flat Agent 18/100 agent aware Front door AI 1/6 silent Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract

Carbon Accounting Greenhouse Gas Scope 3Supply Chain EmissionsProduct Carbon Footprint Sustainability ESG CDP CSRD GHG Protocol Climate Procurement Artificial Intelligence

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 33.0/100 · thin

Contract Quality 11.1 / 19

Developer Ergonomics 2.7 / 15

Access Clarity 5.1 / 15

Operational Transparency 0.5 / 10

Contract Governance 0.9 / 9

Discoverability 4.3 / 8

Regulatory Posture 2.9 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 18/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 0 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Energy & Utilities regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/emitwise/"><img src="https://apis.io/badge/emitwise/card.svg" alt="Emitwise on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

11 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Developer Ergonomics scores 17.9 — up to +16.4 composite points
Access Clarity scores 34.2 — up to +13.2 composite points
Operational Transparency scores 5.3 — up to +12.3 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/emitwise/apis.yml: open an issue on github.com/api-evangelist/emitwise to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Procurement and B2B Buying (source-to-pay suites, spend management)	standard	17.2 (thin)	-	-
Carbon Accounting Disclosure Standards (SBTi, PCAF, CDP, GHG Protocol)	standard	17.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

GHG Protocol

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

Emitwise Facilities API

Physical or virtual locations whose emissions are tracked.

Emitwise Files API

Activity-data file uploads used to calculate emissions.

Emitwise Projects API

Sustainability initiatives that group emissions data.

Emitwise Schema API

Activity data schema definitions.

Emitwise Suppliers API

Aggregated Scope 3 supplier emissions data.

Open Collections 6

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Emitwise API

OPEN COLLECTION

Emitwise Facilities API

OPEN COLLECTION

Emitwise Facilities Files API

OPEN COLLECTION

Emitwise Facilities Projects API

OPEN COLLECTION

Emitwise Facilities Schema API

OPEN COLLECTION

Emitwise Facilities Suppliers API

OPEN COLLECTION

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Emitwise Context

17 classes · 1 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Emitwise — jsonschema rules

5 rules · 4 warnings 1 info

SPECTRAL

JSON Schema 2

Standalone JSON Schema definitions for this provider's data models.

Emitwise Facility

5 properties

JSON SCHEMA

Emitwise Supplier

6 properties

JSON SCHEMA

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Emitwise Authentication

http · 1 scheme

SECURITY

Emitwise Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Emitwise Agentic Access

7 operations · 1 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

APIPortal

APIPortal

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

Build 1

SDKs, sample code, and the tooling you integrate with

GitHub

GitHub

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

Contact

Contact

Commercial 2

Pricing, plans, and the legal terms of use

Privacy

Privacy

TermsOfService

TermsOfService

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 4

Properties that don't map to a standard resource type

Dashboard

PCFCalculator

CookiePolicy

ParentCompany

Source (apis.yml)

aid: emitwise
name: Emitwise
description: Emitwise is a London-based carbon accounting and Scope 3 reporting platform that uses AI to help large enterprises
  measure, manage, and reduce their product carbon footprint (PCF) and supply-chain greenhouse-gas emissions. The platform
  ingests spend data, activity data, and supplier information, auto-classifies suppliers, and produces audit-ready emissions
  reporting aligned with the GHG Protocol (Scope 1, 2, and 3) and frameworks such as CDP and CSRD. The Emitwise developer
  API at api.emitwise.com exposes facilities, projects, activity-data files, schema metadata, and aggregated supplier emissions
  data so customers can integrate carbon accounting into procurement, ERP, and sustainability reporting systems. Access is
  granted per-customer through Emitwise CSMs; API keys are generated from the Company settings area of the dashboard. In July
  2025, Emitwise was acquired by Green Project Technologies; the Emitwise platform and team are now part of Green Project's
  end-to-end decarbonization solutions, while the existing Emitwise developer portal and API endpoints remain live for customers.
type: Index
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
position: Producing
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/emitwise.png
x-docs-platform: docusaurus
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-03
tags:
- Carbon Accounting
- Greenhouse Gas
- Scope 3
- Supply Chain Emissions
- Product Carbon Footprint
- Sustainability
- ESG
- CDP
- CSRD
- GHG Protocol
- Climate
- Procurement
- Artificial Intelligence
tags_raw:
- Carbon Accounting
- Greenhouse Gas
- Scope 3
- Supply Chain Emissions
- Product Carbon Footprint
- Sustainability
- ESG
- CDP
- CSRD
- GHG Protocol
- Climate
- Procurement
- AI
url: https://raw.githubusercontent.com/api-evangelist/emitwise/refs/heads/main/apis.yml
created: '2026-05-25'
modified: '2026-05-25'
specificationVersion: '0.23'
apis:
- aid: emitwise:emitwise-facilities-api
  name: Emitwise Facilities API
  description: Physical or virtual locations whose emissions are tracked.
  humanURL: https://docs.emitwise.com/
  tags:
  - Facilities
  properties:
  - type: OpenAPI
    url: openapi/emitwise-facilities-api-openapi.yml
  - type: Documentation
    url: https://docs.emitwise.com/
  - type: Documentation
    url: https://docs.emitwise.com/v1
  - type: Authentication
    url: https://docs.emitwise.com/#authentication
  - type: Signup
    url: https://docs.emitwise.com/#requesting-access
  - type: JSONSchema
    url: json-schema/emitwise-facility-schema.json
  - type: JSONSchema
    url: json-schema/emitwise-supplier-schema.json
  - type: JSONLD
    url: json-ld/emitwise-context.jsonld
- aid: emitwise:emitwise-files-api
  name: Emitwise Files API
  description: Activity-data file uploads used to calculate emissions.
  humanURL: https://docs.emitwise.com/
  tags:
  - File
  tags_raw:
  - Files
  properties:
  - type: OpenAPI
    url: openapi/emitwise-files-api-openapi.yml
  - type: Documentation
    url: https://docs.emitwise.com/
  - type: Documentation
    url: https://docs.emitwise.com/v1
  - type: Authentication
    url: https://docs.emitwise.com/#authentication
  - type: Signup
    url: https://docs.emitwise.com/#requesting-access
  - type: JSONSchema
    url: json-schema/emitwise-facility-schema.json
  - type: JSONSchema
    url: json-schema/emitwise-supplier-schema.json
  - type: JSONLD
    url: json-ld/emitwise-context.jsonld
- aid: emitwise:emitwise-projects-api
  name: Emitwise Projects API
  description: Sustainability initiatives that group emissions data.
  humanURL: https://docs.emitwise.com/
  tags:
  - Project
  tags_raw:
  - Projects
  properties:
  - type: OpenAPI
    url: openapi/emitwise-projects-api-openapi.yml
  - type: Documentation
    url: https://docs.emitwise.com/
  - type: Documentation
    url: https://docs.emitwise.com/v1
  - type: Authentication
    url: https://docs.emitwise.com/#authentication
  - type: Signup
    url: https://docs.emitwise.com/#requesting-access
  - type: JSONSchema
    url: json-schema/emitwise-facility-schema.json
  - type: JSONSchema
    url: json-schema/emitwise-supplier-schema.json
  - type: JSONLD
    url: json-ld/emitwise-context.jsonld
- aid: emitwise:emitwise-schema-api
  name: Emitwise Schema API
  description: Activity data schema definitions.
  humanURL: https://docs.emitwise.com/
  tags:
  - Schema
  properties:
  - type: OpenAPI
    url: openapi/emitwise-schema-api-openapi.yml
  - type: Documentation
    url: https://docs.emitwise.com/
  - type: Documentation
    url: https://docs.emitwise.com/v1
  - type: Authentication
    url: https://docs.emitwise.com/#authentication
  - type: Signup
    url: https://docs.emitwise.com/#requesting-access
  - type: JSONSchema
    url: json-schema/emitwise-facility-schema.json
  - type: JSONSchema
    url: json-schema/emitwise-supplier-schema.json
  - type: JSONLD
    url: json-ld/emitwise-context.jsonld
- aid: emitwise:emitwise-suppliers-api
  name: Emitwise Suppliers API
  description: Aggregated Scope 3 supplier emissions data.
  humanURL: https://docs.emitwise.com/
  tags:
  - Suppliers
  properties:
  - type: OpenAPI
    url: openapi/emitwise-suppliers-api-openapi.yml
  - type: Documentation
    url: https://docs.emitwise.com/
  - type: Documentation
    url: https://docs.emitwise.com/v1
  - type: Authentication
    url: https://docs.emitwise.com/#authentication
  - type: Signup
    url: https://docs.emitwise.com/#requesting-access
  - type: JSONSchema
    url: json-schema/emitwise-facility-schema.json
  - type: JSONSchema
    url: json-schema/emitwise-supplier-schema.json
  - type: JSONLD
    url: json-ld/emitwise-context.jsonld
common:
- type: AgenticAccess
  url: agentic-access/emitwise-agentic-access.yml
- type: DomainSecurity
  url: security/emitwise-domain-security.yml
- type: Authentication
  url: authentication/emitwise-authentication.yml
- type: Website
  url: https://emitwise.com/
- type: Documentation
  url: https://docs.emitwise.com/
- type: APIPortal
  url: https://docs.emitwise.com/
- type: Dashboard
  url: https://dash.emitwise.com/
- type: PCFCalculator
  url: https://emitwise.com/pcf-calculator/
- type: Solutions
  url: https://emitwise.com/solutions/procurewise-supply-chain-emissions/
- type: Privacy
  url: https://emitwise.com/privacy/
- type: TermsOfService
  url: https://emitwise.com/terms/
- type: CookiePolicy
  url: https://emitwise.com/cookie-policy/
- type: Blog
  url: https://emitwise.com/home/feed/
- type: ParentCompany
  url: https://www.greenprojecttech.com/
- type: Contact
  url: https://www.greenprojecttech.com/contact/get-in-touch
- type: GitHub
  url: https://github.com/emitwise
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Emitwise API — frequently asked questions

Does Emitwise have an API?

Yes. APIs.io lists 5 APIs from Emitwise, including Emitwise Facilities API, Emitwise Files API and Emitwise Projects API, and 2 more.

Is there an OpenAPI specification for the Emitwise API?

Yes. APIs.io indexes 5 OpenAPI specifications for Emitwise, each linked for download from this page.

How do I authenticate with the Emitwise API?

Emitwise uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Emitwise Authentication.

Is the Emitwise API ready for AI agents?

Emitwise has a Kin Score of 33.0 out of 100 (thin) and an Agent Readiness score of 18.4 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/emitwise"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/emitwise/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/emitwise/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.