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

# CarbonDoomsDay

The CarbonDoomsDay API serves daily atmospheric carbon dioxide measurements, exposing the full series of readings and a lookup for a single date. It provides the raw CO2 concentration record for building climate dashboards and trend analyses. Agents can pull current and historical CO2 levels for reporting without scraping observatory data themselves.

## For AI agents

Retrieve the daily atmospheric CO2 measurement series or a single date's reading from CarbonDoomsDay. Returns CO2 concentration records for an agent to chart or summarize.

## Scope

Does not handle emissions forecasting, weather data, or air quality indices. Use for reading daily atmospheric CO2 measurements only.

## Capabilities

- Retrieve the series of daily atmospheric CO2 measurements
- Look up the CO2 measurement for a specific date
- Page through historical CO2 readings

## Use cases

### Agent-Driven Climate Data Lookup

An AI agent answers questions about atmospheric CO2 by pulling the daily measurement series or a single date's reading. It can report the latest level, retrieve a specific day, or gather a range for context. This gives an agent a direct source of CO2 data for climate reporting without scraping observatory sites.

Example prompt: Fetch the most recent CO2 reading and the value for a requested date, then report both with the change between them

### CO2 Trend Reporting

Dashboards and reports pull the daily CO2 series and chart it over time. The API returns readings that a job can page through to assemble a history, which then feeds a recurring trend report. This suits a scheduled task that refreshes a climate dashboard with the latest measurements.

Example prompt: Page through the daily CO2 readings for a date range and produce a time series for a trend chart

### Date-Specific Emissions Lookup

An agent retrieves the CO2 measurement for one date to annotate an event or answer a point-in-time question. The single-date lookup returns that day's reading directly. This is the fast path when only one value is needed rather than the whole series.

Example prompt: Look up the CO2 reading for a specific date and return that day's concentration value

## Key resources

- **CO2 series** — The full list of daily atmospheric CO2 measurements, with pagination
- **CO2 by date** — The CO2 measurement for a single requested date

## Why Jentic

- **Setup:** Wiring the CarbonDoomsDay API by hand means handling its HTTP Basic auth and paging the daily series yourself. Through Jentic you install once, import CarbonDoomsDay from the API Directory, and your agent retrieves CO2 measurements by series or by date.
- **Permission scoping:** The API is read-only, so your agent can never change data through it. A rule can scope further to just the series listing or the single-date lookup, and every call it makes is logged.
- **Credential handling:** Any CarbonDoomsDay credential 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 'atmospheric CO2 measurement' or 'CO2 level for a date', and Jentic returns the matching CarbonDoomsDay operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **NOAA** — US climate and weather data from the National Oceanic and Atmospheric Administration
- **AirNow** — US air quality index and pollutant data by location
- **OpenWeatherMap** — Weather and forecast data API for locations worldwide

## FAQ

### What authentication does the CarbonDoomsDay API use?

The CarbonDoomsDay API declares HTTP Basic authentication in its OpenAPI spec. Through Jentic any credential is held encrypted by your own Jentic One instance and attached at call time, so it never reaches the agent's context.

### Can I look up the CO2 level for a specific date with the CarbonDoomsDay API?

Yes. The API exposes a single-date lookup that returns that day's CO2 measurement directly, alongside the full series for gathering a history. An agent can answer a point-in-time question without paging the whole record.

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

The OpenAPI spec does not specify rate limits. Check the CarbonDoomsDay documentation at https://api.carbondoomsday.com for current limits and usage guidance.

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

Yes. The API is read-only, and a rule can further scope your agent to just the series listing or the single-date lookup, so it reaches only the data you intend. Every call the agent makes is logged.

### How do I read CO2 data through Jentic?

Search Jentic for 'atmospheric CO2 measurement', add the CarbonDoomsDay API from the directory, and your agent then retrieves the series or a single date's reading. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Is there a CarbonDoomsDay MCP server?

You don't need an MCP server to give your agent the CarbonDoomsDay API. Jentic connects it directly from the API Directory: import it and your agent reads CO2 measurements. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.
