M3O User Service API

Name: M3O User Service API API
Brand: M3O User Service API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthenticationapiKey10 EndpointsREST

For Agents

Create and manage user accounts, authenticate logins, reset passwords, and verify email addresses through M3O's microservice user store.

Connect the M3O User Service API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the M3O User Service 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.

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 M3O User Service API API.

Create user accounts with username, email, and password via the /user/Create endpoint

Authenticate users and return session tokens through /user/Login

Reset forgotten passwords with /user/ResetPassword and dispatch verification mail via /user/SendVerificationEmail

Verify a user's email address against a confirmation token using /user/VerifyEmail

GET STARTED

Start building with M3O User Service API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for M3O User Service API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for M3O User Service API, keeping it validated and agent-ready. The M3O User Service is a microservice API for user account management, authentication, and session handling. It exposes endpoints for creating, reading, updating, deleting and listing users alongside login, logout, password reset, email verification and verification email dispatch. Note: the M3O platform has been discontinued; this spec documents the API as it existed for archival and reference use.

Use Cases

Patterns agents use M3O User Service API API for, with concrete tasks.

★ User Registration and Login Flow

Stand up a complete signup and signin flow without operating an auth database. The /user/Create endpoint stores the account, /user/SendVerificationEmail dispatches a confirmation link, /user/VerifyEmail consumes the token, and /user/Login returns a session for authenticated calls. Suitable for prototypes and internal tools that need basic authentication without rolling a custom identity stack.

Call POST /user/Create with a new email and password, then POST /user/SendVerificationEmail to dispatch the confirmation link

Password Reset Workflow

Drive a self-service password reset from an agent or chatbot. The agent collects the user's email, calls /user/ResetPassword to generate a reset token, and confirms the change once the user supplies the new password. The endpoint returns success status so the agent can report the outcome back to the user without requiring access to credential storage.

Submit POST /user/ResetPassword with the user's email to issue a reset token and complete the password change

Administrative User Lookup

Run support and administrative queries against the user store. The /user/Read endpoint fetches a single record by ID, /user/List paginates across the full user base, and /user/Update writes profile changes. Useful for support agents handling account inquiries who need to inspect or amend a specific user without direct database access.

Call POST /user/Read with the target user ID to retrieve the profile, then POST /user/Update to apply the requested change

AI Agent User Management Integration

Let an AI agent provision and manage user accounts on behalf of an operator without handling raw API keys. Through Jentic, the agent searches for the user operation it needs, loads the schema for /user/Create, /user/Login or /user/Delete, and executes the call with credentials brokered by the Jentic vault. The agent never sees the M3O API key directly.

Search Jentic for 'create a user account', load the /user/Create schema, and execute with the supplied email and password

Key Endpoints

10 endpoints — jentic publishes the only available openapi specification for m3o user service api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/user/Create

Create a new user account

POST

/user/Login

Authenticate a user and return a session

POST

/user/ResetPassword

Reset a user's password

POST

/user/VerifyEmail

Verify a user's email address

POST

/user/SendVerificationEmail

Dispatch a verification email

POST

/user/Read

Read a single user record

POST

/user/List

List user accounts

POST

/user/Logout

Terminate an active session

POST

/user/Create

Create a new user account

POST

/user/Login

Authenticate a user and return a session

POST

/user/ResetPassword

Reset a user's password

POST

/user/VerifyEmail

Verify a user's email address

POST

/user/SendVerificationEmail

Dispatch a verification email

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 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. 'create a user account' or 'reset a password') and Jentic returns the matching M3O User Service operations along with their input schemas, so the agent can call the correct endpoint without reading docs.

Time to first call

Direct M3O integration: 1-2 days to wire auth, error handling and request shaping. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Auth0 Authentication API

Production-grade hosted authentication with full OAuth, OIDC and MFA support

Choose Auth0 when the workload needs an actively maintained identity provider, social logins, MFA or enterprise SSO rather than a discontinued microservice.

Alternative

Supabase API

Open-source backend-as-a-service that bundles auth, database and storage

Pick Supabase when the agent needs user accounts plus a Postgres database and storage in one platform, rather than a standalone user microservice.

Alternative

Clerk API

Drop-in user management with prebuilt UI components for modern apps

Use Clerk when the application needs hosted sign-up flows, organisations and session management with minimal backend work.

Complementary

SendGrid Mail API

Transactional email delivery for verification and password-reset messages

Pair with the user service when you want to control verification and reset email content rather than rely on the built-in M3O mailer.

FAQs

Specific to using M3O User Service API API through Jentic.

Why is there no official OpenAPI spec for M3O User Service API?

M3O does not publish an OpenAPI specification, and the platform itself has been discontinued. Jentic generates and maintains this spec so that AI agents and developers can call the M3O User Service via structured tooling. It is validated against the documented API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the M3O User Service API use?

The M3O User Service uses an API key passed in a request header (the apiKey scheme defined in the spec). Through Jentic the key is held in the encrypted MAXsystem vault, so an agent calls /user/Create or /user/Login with a scoped token rather than handling the raw M3O key.

Can I reset a user's password with the M3O User Service API?

Yes. POST /user/ResetPassword accepts the user's email and triggers a password reset flow, and POST /user/SendVerificationEmail dispatches verification mail. Both run on the standard https://api.m3o.com/v1 base URL.

What are the rate limits for the M3O User Service API?

M3O's published documentation does not expose per-endpoint rate limits, and as the platform is discontinued live limits no longer apply. Treat this spec as a structural reference for the API's surface rather than an SLA.

How do I create a user with the M3O User Service through Jentic?

Run pip install jentic, then search for 'create a user account' to surface POST /user/Create, load the input schema, and execute with the email and password fields. Jentic returns the created user record without exposing the underlying API key.

Is the M3O User Service API still operational?

The M3O platform has been discontinued, so live calls against api.m3o.com will not succeed. The Jentic spec is preserved as a reference for the operations that were available, which is useful for migration planning to a replacement provider.