Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Caiyun Weather API, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.caiyunapp.com%2Fcaiyunapp" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fapi.caiyunapp.com%2Fcaiyunapp" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with Caiyun Weather API.
Retrieve real-time weather conditions including temperature, humidity, wind, and AQI for a coordinate
Pull minute-by-minute precipitation forecasts for the next two hours from radar data
Get hourly weather forecasts including temperature, humidity, wind, and precipitation for a coordinate
Get daily weather forecasts including high/low temperature, sunrise/sunset, and astro details
GET STARTED
Return a comprehensive weather payload combining real-time, minutely, hourly, and daily data in one call
Patterns agents use Caiyun Weather API for, with concrete tasks.
★ Minute-Level Precipitation Nowcasts
Caiyun's minutely endpoint returns precipitation intensity for the next 120 minutes in one-minute steps, derived from radar imagery. An agent can call GET /{token}/{longitude},{latitude}/minutely.json and decide whether to delay a drone flight, an outdoor delivery, or a sports event. This level of granularity is rare among free weather APIs and is the main reason developers integrate Caiyun.
Call GET /{token}/116.4074,39.9042/minutely.json and report whether precipitation intensity exceeds 0.1 mm/min within the next 30 minutes.
Travel and Route Weather Lookups
Pull current and short-term weather along a route for travel planning, ride-hailing, or logistics apps. The agent calls GET /{token}/{longitude},{latitude}/realtime.json for each waypoint to get temperature, wind, visibility, and AQI. Combine with the hourly endpoint when the trip extends over the next two days.
Call GET /{token}/{longitude},{latitude}/realtime.json for the origin, midpoint, and destination of a delivery route and warn if any AQI exceeds 150.
Daily Forecast Widgets
Drive a 7-day forecast widget for a website or app from a single Caiyun call. The /daily.json endpoint returns daily high and low temperature, condition codes, sunrise and sunset, and moon phase. The structured JSON maps directly to UI components without further parsing.
Call GET /{token}/{longitude},{latitude}/daily.json with dailysteps=7 and render the highs, lows, and condition codes for the next week.
Agent-Driven Weather Lookups via Jentic
Connect Caiyun to an AI agent through Jentic so a user can ask 'will it rain in the next hour at this address?' in chat. The agent geocodes the address, searches Jentic for the matching Caiyun operation, loads the schema, and calls minutely.json with the API token kept in your Jentic One instance. The token never appears in the agent's prompt or response.
Use the Jentic Python SDK to search for 'minute precipitation forecast', load the operation, and execute it with a given longitude and latitude.
5 endpoints — jentic publishes the only available openapi specification for caiyun weather api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/{token}/{longitude},{latitude}/realtime.json
Real-time weather conditions
/{token}/{longitude},{latitude}/minutely.json
Minute-level precipitation nowcast for next 2 hours
/{token}/{longitude},{latitude}/hourly.json
Hourly forecast
/{token}/{longitude},{latitude}/daily.json
Daily forecast
/{token}/{longitude},{latitude}/weather.json
Combined real-time, minutely, hourly, daily payload
/{token}/{longitude},{latitude}/realtime.json
Real-time weather conditions
/{token}/{longitude},{latitude}/minutely.json
Minute-level precipitation nowcast for next 2 hours
/{token}/{longitude},{latitude}/hourly.json
Hourly forecast
/{token}/{longitude},{latitude}/daily.json
Daily forecast
/{token}/{longitude},{latitude}/weather.json
Combined real-time, minutely, hourly, daily payload
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Caiyun Weather API by hand means placing your token in the URL path, targeting the v2.5 host, and mapping the realtime, minutely, hourly, and daily routes by coordinate yourself. Through Jentic you install once, import Caiyun from the API Directory, store the token once, and your agent calls it.
Permission scoping
Caiyun carries only the token and coordinates in the URL path rather than a resource id, so you limit the agent to the operations it needs, such as realtime or hourly forecast lookups. The minutely and daily forecast operations are separate and are only available if you include them in the allowed set.
Credential isolation
Your Caiyun API token is stored once, encrypted, by your own Jentic One instance and substituted into the URL path at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'minute precipitation forecast' or 'hourly weather', and Jentic returns the matching Caiyun operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Caiyun Weather API through Jentic.
Why is there no official OpenAPI spec for Caiyun Weather API?
Caiyun (ColorfulClouds) does not publish an OpenAPI specification, only HTML developer docs at open.caiyunapp.com. Jentic generates and maintains this spec so that AI agents and developers can call Caiyun Weather API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Caiyun Weather API use?
The API uses an API token passed as part of the URL path (e.g. /v2.5/{token}/{longitude},{latitude}/realtime.json). You obtain the token from open.caiyunapp.com after creating an application. Jentic stores the token encrypted in the vault and substitutes it at execution time so it never enters the agent's prompt.
Can I get minute-level rain forecasts with the Caiyun Weather API?
Yes. Call GET /{token}/{longitude},{latitude}/minutely.json to receive a 120-element array of one-minute precipitation intensity values (mm/min) plus a human-readable description such as 'Light rain starting in 12 minutes'. This is Caiyun's distinguishing feature.
What are the rate limits for the Caiyun Weather API?
The free developer tier allows up to 1,000 requests per day. Paid tiers raise this quota to tens of thousands per day and reduce per-request latency. Check the open.caiyunapp.com console for your account's current tier and usage.
How do I get a 48-hour hourly forecast through Jentic?
Search Jentic for 'hourly weather forecast' and the GET /{token}/{longitude},{latitude}/hourly.json operation is returned with its schema. Load the operation, then execute it with hourlysteps=48. The standard quickstart is pip install jentic, search, load, execute.
Is the Caiyun Weather API free?
Caiyun offers a free developer tier with a daily quota; high-volume production use requires a paid plan billed by request volume. The minutely endpoint is included on all tiers.
Can I limit what my agent is allowed to do with the Caiyun Weather API?
Yes. Because you run Jentic One yourself, your own rules decide which Caiyun operations and credentials your agent may use, and the API carries only the token and coordinates in the URL path rather than a resource id. You add just the operations the agent needs to the allowed set, such as the realtime or hourly forecast lookups, and leave out the rest. The minutely precipitation and daily forecast operations are separate, so the agent can call them only if you include them. Your Caiyun token is substituted at execution time and never enters the agent's prompt.
Know of an official OpenAPI document? Contribute it →
For Agents
Look up real-time weather, minute-by-minute precipitation nowcasts, and hourly or daily forecasts for any coordinate on Earth and return structured JSON.
Use for: Get the real-time weather for Beijing's latitude and longitude, Find out whether it will rain in the next 30 minutes at my location, Retrieve the hourly forecast for the next 48 hours for a coordinate, Get a 7-day daily weather forecast for a city
Not supported: Does not handle severe-weather alerts, satellite imagery, or historical weather records - use for current and short-term forecast lookups by coordinate only.
Jentic publishes the only available OpenAPI specification for Caiyun Weather API, keeping it validated and agent-ready. Caiyun Weather (ColorfulClouds) provides real-time conditions, minute-level precipitation nowcasts, hourly forecasts, and daily forecasts for any latitude and longitude on Earth. The minutely precipitation endpoint is its most distinctive feature, returning precipitation intensity for the next two hours in one-minute increments based on radar data. All endpoints accept the API token in the URL path and return JSON with localised condition codes.