canonical: https://jentic.com/apis/meteosource.com/meteosource # Meteosource Premium Meteosource is a weather data provider that exposes current conditions, multi-day forecasts, place search, historical weather, weather maps, and air quality through a Premium plan REST surface. Agents query by named place or GPS coordinates and receive structured JSON for each variable, with a separate time-machine endpoint for historical lookups and a map endpoint for raster imagery. The API key is sent in the `Authorization` header. Useful for travel apps, agriculture monitoring, logistics planning, and any flow that needs forecast or historical weather as a data point. ## For AI agents Fetch current weather, multi-day forecasts, historical weather, air quality, and place search by name or GPS coordinates. ## Scope Does not handle weather alerts subscription, severe-storm tracking, or marine forecasts - use for point forecasts, history, place search, air quality, and weather maps only. ## Capabilities - Retrieve current conditions and a multi-day forecast for a named city or GPS coordinate - Look up historical weather for a specific past date with the time-machine endpoint - Search for places by name or by prefix to power autocomplete in a weather UI - Reverse-geocode GPS coordinates to the nearest named location for human-readable summaries - Pull air quality data for a single point alongside the standard weather variables - Render a PNG weather map for a chosen variable and bounding area ## Use cases ### Forecast in a Travel Planning Agent An AI travel agent needs the multi-day forecast for a destination before suggesting an itinerary. Calling GET /point with the destination's name or coordinates returns current and forecast weather variables in a single response, which the agent can summarise back to the user. Pair with /find_places when the user only supplies a free-text city to disambiguate before the lookup. Example prompt: GET /find_places to disambiguate the city, then GET /point for the chosen place_id to fetch the multi-day forecast and summarise it ### Historical Weather Backtesting Logistics, insurance, and agriculture teams often need historical weather for a specific date to validate a claim, model a yield, or audit a delivery delay. The time-machine endpoint returns weather for a single location and a chosen past date so the agent can backfill records without scraping. The response sits alongside the live forecast format, keeping schemas consistent. Example prompt: GET /time_machine with the location and the target past date to retrieve the historical observations for a delivery audit ### Air Quality and Health Alerts Public-health and outdoor-event apps surface air quality alongside weather. Calling GET /air_quality for the user's location returns AQI-style metrics that the agent can use to issue health warnings or adjust event recommendations. Combine with /point for a complete environmental snapshot in one workflow. Example prompt: GET /air_quality for the user's coordinates and emit a health alert when the returned index crosses the configured threshold ### AI Agent Integration via Jentic An AI agent uses Jentic to discover the Meteosource Premium API by intent search ('get the weather forecast'). Jentic returns the /point operation with its input schema, so the agent supplies a place name or coordinates and receives the structured forecast in one load-and-execute step. The Meteosource API key lives in your Jentic One instance and never enters the agent's prompt. Example prompt: Use Jentic to search 'get the weather forecast', load the /point schema, and execute it for the user's destination ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /point | Current and forecast weather for a single point | | GET | /find_places | Search for places by name | | GET | /find_places_prefix | Prefix search for places (autocomplete) | | GET | /nearest_place | Nearest named place for GPS coordinates | | GET | /time_machine | Historical weather for a single location and date | | GET | /air_quality | Air quality for a single point | | GET | /map | PNG weather map for area and variable | ## Key resources - **Point** — Current and forecast weather for a single point - **Time Machine** — Historical weather for a single point and a chosen past date - **Find Places** — Place search by full or partial name - **Nearest Place** — Reverse lookup from GPS coordinates to the nearest named location - **Air Quality** — Air quality data for a single point - **Map** — Raster PNG weather map for a variable and bounding area ## Why Jentic - **Setup:** Wiring Meteosource Premium by hand means reading its Authorization-header key scheme and building each point, history, and place-search query against the /api/v1/premium base yourself. Through Jentic you install once, import Meteosource Premium from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** Meteosource Premium is read-only forecast and place data with no resource id in the URL path, so limit the agent to the operations it needs, such as a point forecast, place search, or air quality lookup. You choose which operations it may call, and none of them change data on your account. - **Credential handling:** Your Meteosource API key is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header 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 a point' or 'find nearby places', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **OpenWeatherMap** — Widely used weather API with current, forecast, and historical endpoints - **WeatherAPI** — Weather API with forecast, history, and astronomy data - **Weatherbit** — Weather data API covering current, forecast, history, and air quality - **Meteostat** — Historical and station-based weather data archive ## FAQ ### What authentication does the Meteosource Premium API use? An API key sent in the `Authorization` header (the `APIKeyHeader` security scheme in the spec). Through Jentic the key is stored in your Jentic One instance and injected into the header at request time, so it never enters the agent's prompt. ### Can I look up the weather for a city by name? Yes. GET /find_places resolves a free-text city name to one or more place records, and GET /point then returns the current and forecast weather for the chosen place. /find_places_prefix supports autocomplete-style prefix searches. ### Is historical weather data available? Yes. GET /time_machine returns weather data for a single location and a specified past date, returning observations in the same shape as the forecast endpoint. ### Can I retrieve air quality alongside weather? Yes. GET /air_quality returns air quality metrics for a single point. Use it side-by-side with /point when you need both weather and AQI in the same workflow. ### How do I fetch a forecast through Jentic? Search Jentic for `get the weather forecast`, load the GET /point operation, and execute it with the place name or GPS coordinates. Jentic returns the structured JSON response. ### Are there published rate limits? The OpenAPI spec does not declare quantitative rate limits. Limits depend on your Meteosource Premium plan - check your dashboard or contact Meteosource support before bulk traffic. ### Can I limit what my agent is allowed to do with the Meteosource Premium API? Yes. Because you run Jentic One yourself, your own rules decide which Meteosource operations the agent may call, so you can grant only the ones a task needs, such as a point forecast, place search, or air quality lookup, and withhold the rest. Every endpoint here is a read-only GET with no resource id in the path, so none of the calls change data on your account. Your Meteosource API key stays in your own instance and is injected into the Authorization header at request time, never entering the agent's prompt.