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

# M3O APIs

M3O was a microservices platform that packaged common backend building blocks as simple RPC-style APIs. Jentic publishes the only available OpenAPI specifications for its User Service and Micro Weather APIs, keeping them validated and agent-ready. The M3O platform has been discontinued, so these specs document the APIs as they existed for reference and migration planning. The User Service covers account creation, login, password reset, and email verification, while the Weather API returns current conditions and multi-day forecasts for any global location.

## For AI agents

An agent can create and manage user accounts, authenticate logins, reset passwords, and verify email addresses through the M3O User Service, and look up current weather conditions or multi-day forecasts for any location through the Micro Weather API. Both are called with a single M3O API key.

## Scope

Use for: Referencing the M3O User Service and Micro Weather API surfaces for basic account management, session handling, and current or short-range weather lookups, or for planning a migration off the discontinued platform.

Not supported:
- social login
- multi-factor authentication
- role-based authorization
- historical weather backfill
- weather alerts
- live production traffic

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| M3O User Service API | identity-auth | 10 | Create and manage user accounts, authenticate logins, reset passwords, and verify email addresses through M3O's microservice user store. |
| Micro Weather API (M3O) | data-enrichment | 2 | Look up current weather conditions and multi-day forecasts for any location worldwide via two POST endpoints from the discontinued M3O microservice. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Register, authenticate, or manage user accounts | micro-user-service | The User Service handles account creation, login, password reset, and email verification. |
| Retrieve current weather or a forecast | weather-api | The Micro Weather API returns point-in-time conditions and multi-day forecasts by location. |

## Cross-API use cases

### Personalized weather briefing per user

Authenticate a user with the M3O User Service, then fetch a forecast for their saved location through the Micro Weather API to deliver a tailored daily briefing. The User Service confirms identity and holds the account record while the Weather API supplies the conditions and forecast text.

Example prompt: Call POST /user/Login to authenticate the user, then POST /weather/Forecast with their saved city and days=3 to return a personalized forecast

### Onboarding flow with weather welcome

Create and verify a new account with the User Service, then greet the user with the current conditions for their sign-up location from the Weather API. The User Service dispatches the verification email and stores the profile while the Weather API returns a friendly opening snippet.

Example prompt: Call POST /user/Create then POST /user/SendVerificationEmail, and call POST /weather/Now for the user's city to include in the welcome message

## Why Jentic

- **Setup:** Wiring M3O by hand means sending its API key on every RPC-style POST across both the User Service and the Micro Weather API. Through Jentic you install once, add the M3O APIs you need from the Jentic directory, store the key once, and your agent calls them.
- **Permission scoping:** You choose which M3O operations the agent may call, so you can allow only current-weather lookups, only account creation, or any subset across both APIs. The agent only reaches the operations in the set your own rules 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, and one key covers both APIs.
- **Discovery method:** Agents search the Jentic directory by intent, such as 'create a user account' or 'get the current weather', and Jentic returns the matching M3O operation with its input schema so the agent calls the right endpoint without reading docs.

## Related vendors

- **Auth0** — Actively maintained identity provider with OAuth, OIDC, and MFA, a live replacement for the M3O User Service.
- **Supabase** — Backend-as-a-service bundling auth, database, and storage, covering the account management M3O offered.
- **WeatherAPI** — Live weather service for current conditions and forecasts, a replacement for the discontinued Micro Weather API.
- **OpenWeatherMap** — Widely used weather provider with global coverage, an alternative to the M3O weather endpoints.

## FAQ

### What is M3O and is it still operational?

M3O was a microservices platform that exposed common backend functions, including user management and weather lookup, as simple POST-based APIs. The platform has been discontinued, so live calls against api.m3o.com will not succeed. The specs Jentic maintains are preserved as a structural reference and a starting point for migration planning.

### Which M3O APIs does Jentic cover?

Jentic covers two M3O APIs: the User Service, which handles account creation, login, password reset, and email verification across ten endpoints, and the Micro Weather API, which returns current conditions and multi-day forecasts through two endpoints. Both are documented by Jentic-published OpenAPI specifications.

### Do the two M3O APIs share the same authentication?

Yes. Both the User Service and the Micro Weather API use a single M3O API key passed in a request header, so one credential works across the whole portfolio. Through Jentic the key is stored once in your own Jentic One instance and reused for either API.

### Why does Jentic publish specs for a discontinued platform?

M3O never published its own OpenAPI specifications, so Jentic generated and maintains them. Keeping validated specs available lets developers and agents understand the exact operation surface, which is useful when planning a migration to an actively maintained provider.

### Can I use these M3O APIs in production?

No. Because the M3O platform is discontinued, the endpoints no longer serve live traffic and should not be relied on for production workloads. Use the specs to understand the API structure and to map operations onto a replacement provider such as Auth0 for identity or WeatherAPI for weather.

### How does an agent call the M3O APIs through Jentic?

An agent searches the Jentic directory by intent, such as 'create a user account' or 'get the current weather', and Jentic returns the matching M3O operation with its input schema. The agent then executes the call while your Jentic One instance injects the M3O key, so the raw credential never enters the agent's context.