canonical: https://jentic.com/apis/climatiq.io/climatiq

# Climatiq API

Jentic publishes the only available OpenAPI specification for Climatiq API, keeping it validated and agent-ready. Climatiq turns activity data - kilometres travelled, kilowatt-hours consumed, kilograms of material moved - into greenhouse gas emission estimates by applying peer-reviewed emission factors. The spec exposes three endpoints: a search over the emission factor database, a single estimate call, and a batch estimate call for high-volume workloads. Authentication is HTTP bearer with a Climatiq API key, and the API is well suited to sustainability dashboards, freight calculators, and AI agents that need a defensible carbon number for an activity.

## For AI agents

Estimate greenhouse gas emissions for activities like travel, freight, and energy use, or search the underlying emission factor database. Three endpoints: search, estimate, and batch estimate.

## Scope

Does not handle carbon credit trading, ESG reporting filings, or company-level disclosure data - use for activity-based emissions calculation only.

## Capabilities

- Search the Climatiq emission factor database by activity, region, or source
- Estimate CO2-equivalent emissions for a single activity such as a freight leg or a flight
- Submit batch estimate requests to score many activities in one call
- Attach a peer-reviewed emission factor and source to every calculated number for audit trails
- Power agent-driven sustainability questions with structured, citable carbon estimates

## Use cases

### Freight Carbon Calculator

Logistics platforms need to display per-shipment CO2 figures alongside cost and ETA. Climatiq /data/v1/estimate accepts a freight activity (mode, distance, weight, region) and returns CO2-equivalent emissions sourced from a named emission factor, so the platform can show a defensible carbon number with a citation rather than a vague estimate.

Example prompt: POST /data/v1/estimate with mode=road, distance_km=500, weight_kg=20000 and parse co2e and co2e_unit from the response

### Sustainability Dashboard for Energy Use

Operations teams tracking facility energy use need to convert kWh figures into CO2-equivalent values across regions where the grid mix differs significantly. Climatiq's emission factor search lets the dashboard pick the right factor per region, and /data/v1/estimate calculates the resulting emissions with the source explicitly tagged for each line.

Example prompt: Search /data/v1/search for grid electricity factor in DE then call /data/v1/estimate with energy=12000 kWh to return CO2e for that facility

### Bulk Emissions Backfill

Companies running their first carbon report often need to score hundreds or thousands of historical activities (flights, fuel purchases, freight legs) in one pass. /data/v1/estimate/batch accepts a list of activities in a single request and returns parallel results, which is far more efficient than looping single estimate calls and avoids repeated round-trips.

Example prompt: POST /data/v1/estimate/batch with an array of 500 historical travel activities and store the returned co2e values in the reporting warehouse

### Agent-Driven Carbon Questions

An AI agent in a finance copilot uses Jentic to answer what is the carbon impact of this purchase questions. Jentic routes the intent to Climatiq's estimate endpoint, the agent loads the schema, executes the bearer-authenticated POST, and returns the CO2-equivalent value with the underlying emission factor source so the answer is auditable.

Example prompt: Use Jentic to search for estimate emissions for an activity, load the schema for POST /data/v1/estimate, and execute with the activity payload

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /data/v1/search | Search emission factors by activity, region, and source |
| POST | /data/v1/estimate | Calculate emissions for a single activity |
| POST | /data/v1/estimate/batch | Calculate emissions for a batch of activities |

## Key resources

- **Search** — Look up emission factors in the Climatiq database by activity, region, year, and source
- **Estimate** — Single-activity emissions calculation that returns CO2e and the chosen emission factor
- **Batch Estimate** — Calculate emissions for many activities in one request

## Why Jentic

- **Setup:** Wiring the Climatiq API by hand means managing its bearer token against api.climatiq.io and shaping the activity object for each estimate request yourself. Through Jentic you install once, import the Climatiq API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Climatiq takes the activity and parameters in the request body of its estimate operations, so scope the agent to the operations it needs, such as searching emission factors and estimating a single activity. You choose which operations are in the allowed set, so batch estimation is not callable unless you add it.
- **Credential handling:** Your Climatiq API key is stored once, encrypted, by your own Jentic One instance and injected as the bearer token at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'calculate freight emissions' or 'search emission factors', and Jentic returns the matching Climatiq operation with its input schema, including the activity object structure, so the agent calls it correctly without browsing the reference docs.

## Related APIs

- **Climate Tracker Initiative ESG Data API** — Returns reported company-level Scope 1-3 emissions; pairs with Climatiq when reported figures are unavailable
- **Climate FieldView** — On-farm operation data that can feed agriculture-sector emissions calculations
- **ClinchPad** — Different domain (sales pipeline); included as catalog neighbor

## FAQ

### Why is there no official OpenAPI spec for Climatiq API?

Climatiq does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Climatiq API 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 Climatiq API use?

Climatiq uses HTTP bearer authentication. Send your Climatiq API key as Authorization: Bearer YOUR_KEY on calls to /data/v1/search, /data/v1/estimate, and /data/v1/estimate/batch. Through Jentic the key is held encrypted in your Jentic One instance and injected at execution time.

### Can I calculate emissions for a batch of activities in one call?

Yes. POST /data/v1/estimate/batch accepts an array of activities and returns the CO2-equivalent value plus the emission factor used for each one, in the same order. This is the right endpoint for annual reporting backfills and any workload above a few dozen activities.

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

The OpenAPI spec does not list specific numeric rate limits. In practice Climatiq applies per-plan limits documented on its website. Implement exponential backoff on 429 responses and prefer the batch endpoint over many single-estimate calls to stay under typical limits.

### How do I estimate CO2 for a freight leg through Jentic?

Run pip install jentic, search Jentic for estimate freight emissions, load the schema for POST /data/v1/estimate, and execute with a freight activity payload (mode, distance, weight, region). Jentic injects the bearer token from the vault. Get started with Jentic One, the self-hosted execution layer.

### Are Climatiq estimates auditable?

Yes. The estimate response includes the emission factor that was applied, its source, region, and year, so every CO2 figure can be traced back to a specific peer-reviewed factor in the Climatiq database. This is the main reason teams use Climatiq over a hand-coded calculation.

### Can I limit what my agent is allowed to do with the Climatiq API?

Yes. Because Jentic One is self-hosted, you decide which Climatiq operations your agent may call, so you can allow it to search emission factors and estimate a single activity while leaving batch estimation out of the allowed set. Any operation you do not add stays uncallable, and your stored Climatiq API key is injected only for the operations you permit. Your own rules, not the agent, decide what runs.