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.

M3O APIs for AI Agents

Identity AuthAuthenticationData TransformationJentic-Generated SpecsAPI keyAgent Ready

m3o.com·Developer portal → m3o.com

M3O API Catalog

2 APIs across 2 product groups. All share one credential.

Data Enrichment1

Micro Weather API (M3O)Look up current weather conditions and multi-day forecasts for any location worldwide via two POST endpoints from the discontinued M3O microservice.~2 endpoints

Identity Auth1

M3O User Service APICreate and manage user accounts, authenticate logins, reset passwords, and verify email addresses through M3O's microservice user store.~10 endpoints

Which M3O API should I use?

I want to...	Use	Why
Register, authenticate, or manage user accounts	M3O User Service API	The User Service handles account creation, login, password reset, and email verification.
Retrieve current weather or a forecast	Micro Weather API (M3O)	The Micro Weather API returns point-in-time conditions and multi-day forecasts by location.

Install Jentic One Beta

Connect the M3O APIs to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the M3O APIs, 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%2Fm3o.com" | sh

Step 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%2Fm3o.com" | 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.

Once connected, ask your agent something like: “manage user accounts and look up weather with m3o”.

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

FAQs

Specific to using M3O APIs through Jentic.

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.

BOOK A DEMO

Start Connecting APIs to Your AI Agents

Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.

Book a Demo

For Agents

APIs2 in catalogue

Endpoints12 indexed

AuthAPI key — 1 credential for all 2 APIs

ProvenanceJentic-generated specs

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.

M3O bundled discrete backend functions such as user management and weather lookup into uniform POST-based microservice APIs sharing one key and one host. The platform has been discontinued, so these Jentic-maintained specs serve as a structural reference and a starting point for migrating to actively maintained replacements.

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

Credentials: Both APIs authenticate with a single M3O API key passed in a request header, so one credential covers the entire portfolio.

What AI Agents Can Do with M3O

Each workflow spans multiple M3O APIs. Jentic routes each operation to the right API automatically.

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

APIs used

M3O User Service API + Micro Weather API (M3O)

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.