canonical: https://jentic.com/apis/pirateweather.net/pirateweather

# Pirate Weather API

Weather forecast and historical weather data API providing current conditions, minutely, hourly, and daily forecasts. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get weather forecast, get historical weather data. Covers 2 operations with apiKey authentication.

## Scope

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

## Capabilities

- Retrieve current conditions and multi-day forecasts for any coordinate pair
- Query historical weather data for past dates at specific locations
- Access minutely precipitation intensity for the next hour
- Pull hourly forecast data including temperature, wind, and humidity
- Get daily high/low temperatures, sunrise, sunset, and moon phase data

## Use cases

### Location-Based Weather Forecasting

Retrieve current conditions, minutely precipitation, hourly forecasts, and daily summaries for any latitude/longitude pair. The forecast endpoint returns temperature, precipitation probability, wind speed, humidity, and UV index data in a single call, suitable for travel planning apps, agricultural tools, or outdoor event scheduling.

Example prompt: Call GET `/forecast/{apikey}/45.42`,-75.69 to retrieve the current conditions and 7-day forecast for Ottawa, Canada

### Historical Weather Lookups

Query past weather conditions for any date and location using the time machine endpoint. Returns the same data structure as the forecast endpoint but for a historical timestamp, enabling weather-dependent analytics, insurance claim verification, or agricultural yield correlation studies.

Example prompt: Call GET `/forecast/{apikey}/40.71`,-74.01,1672531200 to retrieve weather conditions in New York on January 1, 2023

### AI Agent Integration via Jentic

AI agents discover and call Pirate Weather 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 weather forecast', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/forecast/{apikey}/{latitude},{longitude}` | Get weather forecast |
| GET | `/forecast/{apikey}/{latitude},{longitude},{time}` | Get historical weather data |

## Key resources

- **Forecast** — Operations for forecast

## Why Jentic

- **Setup:** Wiring Pirate Weather by hand means placing your API key directly in the request path, formatting latitude and longitude into the URL, and handling retries yourself. Through Jentic you install once, import Pirate Weather from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Pirate Weather offers read-only forecast lookups, so you limit the agent to the operations it needs, such as fetching a forecast for a set of coordinates. Because you pick the allowed operations, the agent reads forecasts and nothing else.
- **Credential handling:** Your Pirate Weather API key is stored once, encrypted, by your own Jentic One instance and injected into the request path at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get the weather forecast for these coordinates', and Jentic returns the matching Pirate Weather 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 Pirate Weather API use?

The Pirate Weather API uses an API key passed in the `apikey` path. 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 weather forecast with the Pirate Weather API?

Yes. Use the GET `/forecast/{apikey}/{latitude}`,{longitude} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Pirate Weather 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 weather forecast through Jentic?

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

### How many endpoints does the Pirate Weather API have?

The Pirate Weather API exposes 2 endpoints covering forecast operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which Pirate Weather operations your agent can call, and you store the API key in your own instance so it never reaches the agent's context. The Pirate Weather API offers only read-only lookups, so you can allow just the forecast call, GET `/forecast/{apikey}/{latitude}`,{longitude}, while withholding the historical time machine lookup, GET `/forecast/{apikey}/{latitude}`,{longitude},{time}. With the allowed operations pinned to what the task needs, the agent reads the forecasts you permit and nothing else.