canonical: https://jentic.com/apis/qweather.com/qweather

# QWeather API

Location-based weather data API providing real-time weather, forecasts, air quality, weather warnings, weather indices, minutely precipitation, tropical cyclones, ocean data, astronomy, and geolocation services. The API exposes 12 endpoints secured with bearer authentication.

## For AI agents

Programmatically get real-time weather, get daily weather forecast. Covers 12 operations with bearer authentication.

## Scope

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

## Capabilities

- Get real-time weather
- Access QWeather API data enrichment resources via REST API
- Query QWeather API endpoints with structured JSON responses
- Authenticate requests with bearer credentials managed by Jentic
- Access QWeather API resources programmatically via REST

## Use cases

### Data Enrichment Operations

Use the QWeather API to perform data enrichment operations programmatically. The API provides 12 endpoints covering core functionality including get real-time weather, get daily weather forecast, get hourly weather forecast.

Example prompt: Call GET `/v7/weather/now` to get real-time weather

### Automated GeoAPI Management

Automate geoapi operations by combining multiple QWeather API endpoints. Agents can get daily weather forecast and then get hourly weather forecast in a single workflow.

Example prompt: Call GET `/v7/weather/{days}d` to get daily weather forecast, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call QWeather 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 bearer tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v7/weather/now` | Get real-time weather |
| GET | `/v7/weather/{days}d` | Get daily weather forecast |
| GET | `/v7/weather/{hours}h` | Get hourly weather forecast |
| GET | `/v7/minutely/5m` | Get minutely precipitation forecast |
| GET | `/v7/warning/now` | Get active weather warnings |
| GET | `/v7/indices/{days}d` | Get weather lifestyle indices |
| GET | `/v7/air/now` | Get real-time air quality |
| GET | `/v7/air/{days}d` | Get air quality forecast |

## Key resources

- **GeoAPI** — City lookup and geolocation services
- **Real-time Weather** — Current weather observations
- **Weather Forecast** — Daily and hourly weather forecasts
- **Minutely Forecast** — Minute-level precipitation forecasts
- **Weather Warning** — Severe weather warnings and alerts

## Why Jentic

- **Setup:** Wiring the QWeather API by hand means learning its bearer auth, choosing between the api.qweather.com and geoapi.qweather.com hosts, and handling retries across its weather, air, and warning reads yourself. Through Jentic you install once, import QWeather from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** QWeather drives its forecasts through request parameters such as location rather than a resource id in the path, so limit the agent to the operations it needs, such as current weather or an air quality read. You choose which operations are allowed, so the agent reaches only what you list.
- **Credential handling:** Your QWeather token 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 the current weather for a city' or 'check air quality', and Jentic returns the matching QWeather 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 QWeather API use?

The QWeather API uses a Bearer token in the Authorization 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 real-time weather with the QWeather API?

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

### What are the rate limits for the QWeather 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 real-time weather through Jentic?

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

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

The QWeather API exposes 12 endpoints covering geoapi, real-time weather, weather forecast operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which QWeather operations and credentials the agent can use. QWeather drives its reads through request parameters like location rather than a resource id in the path, so you list only the operations the agent needs, such as GET `/v7/weather/now` for current weather or GET `/v7/air/now` for air quality, and leave out forecasts or weather warnings. The agent can reach only the operations you allow, and your stored token is injected at execution time without entering the agent's context.