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.