Meteosource Premium

✓ Official Vendor SpecData EnrichmentAddress ValidationapiKey7 EndpointsREST

For Agents

Fetch current weather, multi-day forecasts, historical weather, air quality, and place search by name or GPS coordinates.

Install Jentic One Beta

Connect the Meteosource Premium to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Meteosource Premium, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Meteosource Premium API.

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

GET STARTED

Start building with Meteosource Premium API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Meteosource Premium API for, with concrete tasks.

★ 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.

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.

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.

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.

Use Jentic to search 'get the weather forecast', load the /point schema, and execute it for the user's destination

Key Endpoints

7 endpoints — 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.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Meteosource Premium API through Jentic.

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.