Micro Weather API (M3O)

Name: Micro Weather API (M3O) API
Brand: Micro Weather API (M3O)
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentData TransformationapiKey2 EndpointsREST

For Agents

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

Connect the Micro Weather API (M3O) to your agent

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

Install Jentic One Beta (Self-Hosted)

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

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 Micro Weather API (M3O) API.

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

GET STARTED

Start building with Micro Weather API (M3O) API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Micro Weather API (M3O), keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Micro Weather API (M3O) API for, with concrete tasks.

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

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.

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.

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

2 endpoints — jentic publishes the only available openapi specification for micro weather api (m3o), keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/weather/Now

Return current weather conditions for a location

POST

/weather/Forecast

Return a multi-day forecast for a location

POST

/weather/Now

Return current weather conditions for a location

POST

/weather/Forecast

Return a multi-day forecast for a location

Why though Jentic?

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

Credential isolation

M3O API keys are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — the raw API key never enters the agent's context, so a leaked prompt cannot leak the underlying credential.

Intent-based discovery

Agents search by intent (e.g. 'get the current weather' or 'get a 5 day forecast') and Jentic returns the matching M3O Weather operations along with their input schemas.

Time to first call

Direct M3O integration: 1-2 hours for two endpoints. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

WeatherAPI

Live alternative for current conditions, forecasts and historical weather

Choose WeatherAPI when the workload needs a live, actively maintained weather service rather than the discontinued M3O platform.

Alternative

OpenWeatherMap API

Widely used weather provider with global coverage and a generous free tier

Pick OpenWeatherMap when the agent needs broad endpoint coverage including air quality, alerts and One Call summaries.

Alternative

Visual Crossing Weather API

Forecast and historical weather across decades of data

Use Visual Crossing when the workload needs historical weather backfill, which the discontinued M3O endpoint never supported.

FAQs

Specific to using Micro Weather API (M3O) API through Jentic.

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 at https://app.jentic.com/sign-up.

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 the encrypted MAXsystem vault, 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.