canonical: https://jentic.com/apis/m3o.com/weather-api

# M3o Micro Weather API (M3O)

Jentic publishes the only available OpenAPI specification for Micro Weather API (M3O), keeping it validated and agent-ready. The Micro Weather API exposes two POST endpoints - one for current conditions and one for multi-day forecasts - covering any global location addressable by city, postal code or coordinates. Note: the M3O platform has been discontinued; this spec documents the API as it existed for reference and migration planning.

## For AI agents

Look up current weather conditions and multi-day forecasts for any location worldwide via two POST endpoints from the discontinued M3O microservice.

## Scope

Does not handle historical weather backfill, weather alerts, air quality readings, or marine forecasts - use for current conditions and short-range forecasts only.

## Capabilities

- Retrieve current temperature, humidity and conditions for a queried location via `/weather/Now`
- Generate multi-day forecasts including daily highs, lows and precipitation through `/weather/Forecast`
- Query weather by city name, postal code or latitude/longitude pair
- Surface condition codes and human-readable descriptions for downstream display logic
- Return wind speed, direction and pressure fields for sensor and aviation use cases

## Use cases

### Current Conditions Lookup

Surface a single point-in-time weather reading inside a chatbot, status page or dashboard. POST `/weather/Now` accepts a location string and returns temperature, humidity, condition text and wind data in one call. Suitable for lightweight integrations that need a quick weather snippet rather than a full forecast feed.

Example prompt: Call POST `/weather/Now` with location 'London, UK' and return the temperature in Celsius and the condition description

### Multi-Day Forecast Generation

Drive trip planning, logistics scheduling or outdoor event prep with a forward-looking forecast. POST `/weather/Forecast` accepts a location plus a number of days and returns an array of daily summaries with highs, lows and precipitation chance. The endpoint is suitable for agents preparing daily briefings or itinerary recommendations.

Example prompt: Call POST `/weather/Forecast` with location 'Madrid' and days=5 to retrieve the daily highs, lows and precipitation probability

### AI Agent Weather Briefing

Give an AI agent the ability to fetch and summarise weather as part of a wider workflow without managing API keys. Through Jentic the agent searches for the weather operation, loads the input schema for `/weather/Now` or `/weather/Forecast`, and executes with credentials brokered by the vault. Useful for travel agents, dispatch tools and morning briefing assistants.

Example prompt: Search Jentic for 'get the weather forecast', load `/weather/Forecast`, and execute for the user's home city for the next 3 days

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/weather/Now` | Return current weather conditions for a location |
| POST | `/weather/Forecast` | Return a multi-day forecast for a location |

## Key resources

- **Current Conditions** — Point-in-time temperature, humidity, wind and condition data via `/weather/Now`
- **Forecast** — Multi-day daily forecast with highs, lows and precipitation through `/weather/Forecast`

## Why Jentic

- **Setup:** Wiring the Micro Weather API by hand means sending its API key on each POST and handling the two calls, current conditions and forecast, against the M3O host. Through Jentic you install once, import the Micro Weather API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** You choose which Micro Weather operations the agent may call, so you can limit it to just current conditions, just the forecast, or both. The agent only reaches the operations in the set you allow.
- **Credential handling:** Your M3O key 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' or 'get a five-day forecast', and Jentic returns the matching Micro Weather operation with its input schema so the agent calls the right endpoint directly.

## Related APIs

- **WeatherAPI** — Live alternative for current conditions, forecasts and historical weather
- **OpenWeatherMap API** — Widely used weather provider with global coverage and a generous free tier
- **Visual Crossing Weather API** — Forecast and historical weather across decades of data

## FAQ

### Why is there no official OpenAPI spec for Micro Weather API (M3O)?

M3O does not publish an OpenAPI specification, and the M3O platform has since been discontinued. Jentic generates and maintains this spec so AI agents and developers can call the Micro Weather API via structured tooling. It is validated against the documented surface and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Micro Weather API use?

The API uses an API key passed as a header (the apiKeyHeader scheme defined in the spec). Through Jentic the key is held in your encrypted Jentic One instance, so an agent calls `/weather/Now` or `/weather/Forecast` with a scoped token rather than handling the raw M3O credential.

### How many days of forecast can the Micro Weather API return?

POST `/weather/Forecast` returns an array of daily summaries based on a days parameter supplied in the request body. The maximum range was capped at the M3O free-tier limit; with the platform discontinued, treat the spec as a structural reference rather than a live SLA.

### What are the rate limits for the Micro Weather API?

M3O previously enforced per-key request quotas tied to plan tier, but those limits no longer apply because the platform is discontinued. The spec is preserved primarily for migration planning to a replacement weather provider.

### How do I get current weather with the Micro Weather API through Jentic?

Run pip install jentic, then search for 'get the current weather' to surface POST `/weather/Now`, load the input schema, and execute with the location field set to a city or coordinate pair. Jentic handles the API key in the background.

### Can the Micro Weather API return historical weather data?

The published spec exposes only `/weather/Now` and `/weather/Forecast` - there is no documented historical endpoint. For backfill or climatology workloads, choose an alternative provider such as Visual Crossing Weather that publishes a history endpoint.

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

Yes. Because you run Jentic One yourself, your own rules decide which Micro Weather operations the agent may call. You can allow only current conditions via POST `/weather/Now`, only multi-day forecasts via POST `/weather/Forecast`, or both, and the agent can reach only the operations in the set you permit. The stored M3O API key is injected at execution time for the calls you have approved, never exposed to the agent directly.