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

# Weatherbit API

Weather API providing current weather observations, forecasts, historical weather data, severe weather alerts, air quality data, and geolocation services from over 120,000 weather stations worldwide. The API exposes 13 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get current weather, get 16-day daily forecast. Covers 13 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for data enrichment only.

## Capabilities

- Get current weather
- Manage data enrichment data programmatically
- Integrate Weatherbit API into automated workflows
- Query and filter Weatherbit API records by parameters
- Monitor Weatherbit API operational status and events

## Use cases

### Data Enrichment Operations

Use the Weatherbit API to perform data enrichment operations programmatically. The API provides 13 endpoints covering core functionality including get current weather, get 16-day daily forecast, get 240-hour hourly forecast.

Example prompt: Call GET /current to get current weather

### Automated Current Weather Management

Automate current weather operations by combining multiple Weatherbit API endpoints. Agents can get 16-day daily forecast and then get 240-hour hourly forecast in a single workflow.

Example prompt: Call GET /forecast/daily to get 16-day daily forecast, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Weatherbit API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get current weather', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /current | Get current weather |
| GET | /forecast/daily | Get 16-day daily forecast |
| GET | /forecast/hourly | Get 240-hour hourly forecast |
| GET | /forecast/minutely | Get minutely precipitation forecast |
| GET | /history/daily | Get daily historical weather |
| GET | /history/hourly | Get hourly historical weather |
| GET | /history/subhourly | Get sub-hourly historical weather |
| GET | /alerts | Get severe weather alerts |

## Key resources

- **Current Weather** — Current weather observations
- **Forecast** — Weather forecasts (daily and hourly)
- **Historical** — Historical weather data
- **Alerts** — Severe weather alerts
- **Air Quality** — Current and forecast air quality data

## Why Jentic

- **Setup:** Wiring the Weatherbit API by hand means learning its API key header, pointing at api.weatherbit.io, and handling responses yourself. Through Jentic you install once, import the Weatherbit API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Weatherbit takes its location in the request rather than in the URL path, so limit the agent to the operations it needs, such as current conditions, forecasts, or history lookups. You choose the operations it may call, so anything beyond what you enable is not available.
- **Credential handling:** Your Weatherbit API key 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 'get current weather' or 'get a daily forecast', and Jentic returns the matching Weatherbit operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Clearbit** — Alternative data enrichment API
- **Fullcontact** — Alternative data enrichment API
- **Hunter** — Complementary data enrichment API

## FAQ

### What authentication does the Weatherbit API use?

The Weatherbit API uses an API key passed in the `X-API-Key` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get current weather with the Weatherbit API?

Yes. Use the GET /current endpoint. The API returns structured JSON responses that agents can parse and act on directly.

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

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get current weather through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get current weather'. Jentic returns the matching Weatherbit API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Weatherbit API have?

The Weatherbit API exposes 13 endpoints covering current weather, forecast, historical operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Weatherbit operations and credentials your agent can use. You can restrict it to only the endpoints it needs, such as current conditions from GET /current, forecasts from GET /forecast/daily or GET /forecast/hourly, or history lookups from GET /history/daily, and leave everything else off. Anything you do not enable stays unavailable to the agent.