canonical: https://jentic.com/apis/carbondoomsday.com/carbondoomsday-carbondoomsday-api # CarbonDoomsDay Jentic publishes the only available OpenAPI specification for CarbonDoomsDay, keeping it validated and agent-ready. CarbonDoomsDay is an open data API that publishes daily atmospheric CO2 readings sourced from the Mauna Loa Observatory. This Jentic-maintained variant of the spec exposes two GET endpoints - list readings with date filtering, and fetch a specific date - packaged for direct use in climate dashboards and agent tooling. Authentication is HTTP basic, and most use cases work without credentials. ## For AI agents Fetch daily Mauna Loa atmospheric CO2 ppm readings for any date or range, packaged through a Jentic-maintained spec. ## Scope Does not handle organisational emissions, carbon offsets, or air quality measurements other than CO2 - use for daily Mauna Loa CO2 ppm readings only. ## Capabilities - List Mauna Loa atmospheric CO2 ppm readings with date filtering and pagination - Retrieve a single CO2 reading for a specific calendar date - Track daily atmospheric CO2 trends for sustainability dashboards - Backfill historical CO2 ppm series for climate visualisations - Drive a 'CO2 today' widget on a public-facing site or status page ## Use cases ### Climate Dashboard CO2 Widget Embed a daily atmospheric CO2 ppm value in a sustainability or climate-awareness dashboard. The /co2 endpoint returns the latest reading and supports date filtering for historical context, while /co2/{date} returns a specific day's value. The response is small and cache-friendly, suitable for hourly polling on a status-page or homepage widget. Example prompt: Fetch the latest CO2 reading from /co2 and return the ppm value with its date as a single sentence. ### Historical CO2 Time Series Build a time series chart by paginating through GET /co2 with date-range filters. The endpoint returns dated ppm values that can be plotted directly in a charting library, giving educational sites and ESG dashboards a defensible, auditable data source for the Keeling Curve without scraping NOAA tables. Example prompt: Pull all CO2 readings for the last 12 months and return them as a list of {date, ppm} pairs. ### AI Agent Climate Q&A via Jentic Wire CarbonDoomsDay into an agent through Jentic so a user question like 'what was atmospheric CO2 last Friday?' becomes a single tool call. Jentic finds the right operation, hands the agent the schema for /co2/{date}, and returns a structured ppm response without the agent needing to know basic-auth or the base URL. Example prompt: Through Jentic, fetch the CO2 reading for 2000-01-01 and return the ppm value. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /co2 | List CO2 readings with filtering and pagination | | GET | /co2/{date} | Get the CO2 reading for a specific date | ## Key resources - **CO2** — Daily atmospheric CO2 ppm readings from Mauna Loa, with list and per-date lookup ## Why Jentic - **Setup:** Wiring CarbonDoomsDay by hand means handling its basic-auth header and calling the api.carbondoomsday.com host for daily CO2 readings yourself. Through Jentic you install once, import CarbonDoomsDay from the API Directory, store the credentials once, and your agent calls it. - **Permission scoping:** CarbonDoomsDay exposes two read operations, so you scope by operation: limit the agent to the ones it needs, such as listing CO2 readings or fetching a single date, and it can do nothing beyond the set you allow. - **Credential handling:** Your CarbonDoomsDay basic-auth credentials are stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get the atmospheric CO2 reading for a date', and Jentic returns the matching CarbonDoomsDay operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **CarbonDoomsDay (apis.guru)** — Same CarbonDoomsDay endpoints, packaged from the apis.guru third-party spec. - **CarbonAPI** — Calculates organisational and product emissions from documents and transactions. - **Carbon REST API** — Carbon 3D printing manufacturing platform; unrelated to atmospheric CO2 but commonly confused. ## FAQ ### Why is there no official OpenAPI spec for CarbonDoomsDay? CarbonDoomsDay does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call CarbonDoomsDay 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 CarbonDoomsDay API use? The OpenAPI spec declares HTTP basic authentication, though endpoints are typically accessible without credentials for read-only public data. Through Jentic, any basic-auth credentials are stored encrypted in the credential vault and injected at execution time, so agents never see raw passwords. ### Where does the CO2 data come from? Readings are sourced from the NOAA Mauna Loa Observatory CO2 measurement program - the dataset that produces the Keeling Curve. CarbonDoomsDay republishes these daily values in JSON form so applications can consume them directly without parsing NOAA's text files. ### Can I get the CO2 reading for a specific date? Yes. Call GET /co2/{date} with a date in YYYY-MM-DD format and the API returns the ppm reading for that day if available. Some historical days may be missing - Mauna Loa has occasional measurement gaps - in which case the endpoint responds with a 404. ### How do I list CO2 readings across a date range? GET /co2 returns readings with pagination and supports filtering by date so you can pull a specific window. Iterate through pages to build a full historical series for a chart or analysis. ### What are the rate limits for the CarbonDoomsDay API? The OpenAPI specification does not declare explicit rate limits. As a public service, treat it gently - cache responses and avoid high-frequency polling. The data only updates daily, so an hourly or daily fetch is sufficient for most dashboards. ### How do I fetch a CO2 reading through Jentic? Run `pip install jentic`, then use Jentic's search to find the CO2 lookup operation with the query "get atmospheric co2 reading", load the schema, and execute with `{"date": "2024-01-15"}`. Jentic calls GET /co2/{date} and returns the ppm value as structured output. ### Can I limit what my agent is allowed to do with the CarbonDoomsDay API? Yes. Jentic One is self-hosted by you, so your own rules decide which of CarbonDoomsDay's two read operations the agent may call. You can allow it to list CO2 readings (GET /co2), to fetch a single date's reading (GET /co2/{date}), or restrict it to just one of these, and it can do nothing beyond the operations you permit. The same self-hosted instance holds the basic-auth credentials and injects them only for the calls you have scoped.