Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Data Enrichment / CarbonAPI
CarbonAPI logo

CarbonAPI

66
AI ReadinessAI-Aware (B)66/100
See full scorecard
Agent-ready OpenAPI document · curated by JenticData EnrichmentData TransformationapiKey4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Submit document and transaction batches to calculate greenhouse-gas emissions for spend-based carbon accounting and freight reporting.

Use for: I need to calculate the carbon footprint of last quarter's expense receipts, Estimate emissions for a batch of supplier invoices, Get kgCO2e for our freight transactions this month, Submit transactions to categorise their carbon impact

Not supported: Does not handle real-time emissions, IoT sensor ingest, or carbon offset purchasing - use for batch-based document and transaction emissions calculation only.

Jentic publishes the only available OpenAPI specification for CarbonAPI, keeping it validated and agent-ready. CarbonAPI is a carbon accounting service that enriches expense, supplier, and freight data with calculated greenhouse-gas emissions. It accepts batches of documents (invoices, receipts, bills) for emissions analysis and batches of structured transactions for category-based emissions estimation, returning kgCO2e values that map to standard carbon-accounting frameworks. Agents can use it to compute the footprint of business spend, freight movements, or supplier activity at scale.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the CarbonAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the CarbonAPI, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

1

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcarbonapi.io%2Fcarbonapi" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fcarbonapi.io%2Fcarbonapi" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with CarbonAPI API.

Submit a batch of receipt and invoice documents for emissions analysis

Retrieve the calculated emissions and extracted line items for a document batch by batch ID

Submit a batch of structured transactions for category-based emissions estimation

Retrieve calculated kgCO2e and per-transaction breakdown for a transaction batch by batch ID

Estimate supplier emissions from transactional data using spend-based methodology

Calculate freight emissions for shipping legs included in a transaction batch

Use Cases

Patterns agents use CarbonAPI API for, with concrete tasks.

★ Spend-Based Emissions Reporting

Convert a finance system's transaction export into a carbon footprint report. Agents post a transaction batch to POST /v1/transactions/batch, then poll GET /v1/transactions/batch/{batchId} for the calculated kgCO2e per transaction. CarbonAPI applies category-based emission factors and returns results that can be aggregated into Scope 1, 2, and 3 dashboards for sustainability reporting.

Post a transaction batch of last month's expenses, poll until processing completes, then return total kgCO2e grouped by category.

Receipt and Invoice Footprint Analysis

Run document-level emissions analysis on receipts and invoices. POST /v1/documents/batch accepts a batch of documents, and GET /v1/documents/batch/{batchId} returns the extracted line items and their calculated emissions. This lets an expense-management or accounting agent attach kgCO2e to every expense without manual categorisation.

Upload 50 receipts as a document batch, wait for processing, and return the top three highest-emission line items.

Freight Emissions for Logistics Reporting

Calculate the emissions of freight movements by submitting them as transactions. CarbonAPI supports freight emissions calculation as part of its transaction batch processing, returning kgCO2e per shipping leg. This feeds logistics dashboards and ESG disclosures with auditable freight footprint figures.

Submit a transaction batch containing freight legs from origin to destination ports and return total kgCO2e.

AI Agent Carbon Accounting via Jentic

Wire CarbonAPI into an agent through Jentic so a CFO or ESG lead can ask 'what is our footprint for Q1?' and the agent fetches the calculation. Jentic returns the right batch endpoint and schema, holds the API key in its vault, and orchestrates the submit/poll cycle so the agent does not need to maintain integration code.

Through Jentic, submit a transaction batch and return the calculated total kgCO2e once results are ready.

Key Endpoints

4 endpoints — jentic publishes the only available openapi specification for carbonapi, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/v1/documents/batch

Create a document batch for emissions analysis

GET

/v1/documents/batch/{batchId}

Get processed document batch results

POST

/v1/transactions/batch

Create a transaction batch for emissions calculation

GET

/v1/transactions/batch/{batchId}

Get processed transaction batch results

POST

/v1/documents/batch

Create a document batch for emissions analysis

GET

/v1/documents/batch/{batchId}

Get processed document batch results

POST

/v1/transactions/batch

Create a transaction batch for emissions calculation

GET

/v1/transactions/batch/{batchId}

Get processed transaction batch results

Jentic AI Readiness Score

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.

C

CarbonAPI

- AI-Aware (B)
66/100
100
Foundational Compliance
63
Developer Experience & Jentic Compatibility
46
AI-Readiness & Agent Experience
94
Agent Usability
50
Security
100
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

63

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4
0%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

46

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4
34%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

50

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1
50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1
100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

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

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring CarbonAPI by hand means passing your key in the Authorization header on every call, submitting document and transaction batches, and polling each batchId for results against the api.carbonapi.io host yourself. Through Jentic you install once, import CarbonAPI from the API Directory, store the key once, and your agent calls it.

Permission scoping

A batch is created from the request body and read back by its batchId, so you scope by operation: limit the agent to the ones it needs, such as submitting a transaction batch and reading its result, and leave document batch calls out of the allowed set until you want them.

Credential isolation

Your CarbonAPI key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'calculate emissions for a batch of transactions', and Jentic returns the matching CarbonAPI operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

CarbonDoomsday

→

Atmospheric CO2 readings from Mauna Loa for sustainability context.

Use alongside CarbonAPI when a dashboard needs both organisational footprint and global atmospheric CO2 trend.

Complementary

Carbon REST API

→

Carbon 3D printing manufacturing platform; unrelated to emissions but sometimes confused.

Choose Carbon REST API for additive manufacturing workflows, not emissions accounting.

Complementary

CarAPI.dev

→

Vehicle data API providing VIN decoding and specs that feed vehicle emissions calculations.

Pair when calculating per-vehicle emissions from a VIN-derived make, model, and fuel type.

FAQs

Specific to using CarbonAPI API through Jentic.

Why is there no official OpenAPI spec for CarbonAPI?

CarbonAPI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CarbonAPI via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the CarbonAPI use?

CarbonAPI uses an API key passed in the `Authorization` header on every request. Through Jentic the key is stored encrypted in the credential vault and injected at execution time, so the raw key never appears in the agent's prompt or chat history.

Can I calculate freight emissions with CarbonAPI?

Yes. Freight emissions are handled through the transaction batch endpoint - submit shipping legs as transactions to POST /v1/transactions/batch and CarbonAPI returns the calculated kgCO2e for each leg in the batch result available at GET /v1/transactions/batch/{batchId}.

Is CarbonAPI synchronous or asynchronous?

CarbonAPI is asynchronous and batch-based. POST endpoints accept a batch and return a batchId; the actual emissions calculation runs in the background. Poll the matching GET /v1/{type}/batch/{batchId} endpoint until the batch reports as processed before reading results.

What are the rate limits for the CarbonAPI?

The OpenAPI specification does not declare explicit rate limits. Limits are tied to the plan associated with your API key - keep batch sizes reasonable and back off on 429 responses. Contact CarbonAPI support for the quota tied to your account.

How do I submit a transaction batch through Jentic?

Run `pip install jentic`, then use Jentic's search to find the transaction batch operation with the query "calculate emissions for transactions", load the schema, and execute with your transaction array. Jentic calls POST /v1/transactions/batch, attaches your CarbonAPI key from the vault, and returns the batchId you can poll.

What's the difference between the documents and transactions endpoints?

The /v1/documents/batch endpoints take unstructured receipts and invoices and extract line items before calculating emissions. The /v1/transactions/batch endpoints take already-structured transaction records (amount, category, supplier) and apply category-based emission factors directly. Use documents when starting from PDFs/images, and transactions when starting from your finance system.

Can I limit what my agent is allowed to do with the CarbonAPI?

Yes. Because you run Jentic One yourself, your own rules decide which CarbonAPI operations and credentials the agent may use, so you scope access by operation. CarbonAPI creates a batch from the request body and reads it back by its batchId, which means you can allow the agent to submit a transaction batch (POST /v1/transactions/batch) and read its result (GET /v1/transactions/batch/{batchId}) while leaving the document batch calls out of the allowed set. Your CarbonAPI key stays with your instance and is injected only when a permitted operation runs, so the agent can only call the endpoints you have approved.

GET STARTED

Start building with CarbonAPI API

Explore with Jentic One
View OpenAPI Document