Install Jentic One Beta

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.

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%2Fmicro-user-service" | 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%2Fmicro-user-service" | 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.

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

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use M3O User Service 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 your Jentic One instance. 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

POST

/user/Read

Read a single user record

POST

/user/List

List user accounts

POST

/user/Logout

Terminate an active session

Why Jentic?

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

Setup

Wiring the M3O User Service API by hand means sending its API key on every RPC-style POST and coordinating it across account creation, login, password reset, and email verification calls. Through Jentic you install once, import the M3O User Service API from the API Directory, store the key once, and your agent calls it.

Permission scoping

You choose which M3O User Service operations the agent may call, so you can limit it to the ones it needs, such as creating a user or sending a verification email, and leave out others like resetting a password unless you add them. The agent only reaches the operations in the set you 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.

Intent-based discovery

Agents search Jentic by intent such as 'create a user account' or 'reset a password', and Jentic returns the matching M3O User Service operation with its input schema so the agent calls the right endpoint without reading docs.

FAQs

Specific to using M3O User Service 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 with Jentic One, the self-hosted execution layer.

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 your encrypted Jentic One instance, 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.

Can I limit what my agent is allowed to do with the M3O User Service API?

Yes. Because Jentic One is self-hosted, you decide which M3O User Service operations the agent may call, so you can allow just the ones it needs, such as /user/Create or /user/SendVerificationEmail, and leave out others like /user/ResetPassword, /user/Delete, or /user/List. The agent can only reach the operations in the set you permit, and the M3O API key stays in your own instance rather than the agent's context. Your own rules decide which endpoints and credentials are in scope for each agent.

M3O User Service API

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

Browse all M3o APIs

Agent-ready OpenAPI document · curated by JenticIdentity AuthAuthenticationapiKey10 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to register a new user account with email and password, Authenticate a user against stored credentials and return a session, Send a verification email to a newly registered account, Reset the password for a user who has forgotten their credentials

Not supported: Does not handle social login, multi-factor authentication, role-based authorization, or organisation hierarchies - use for basic user account and session management only.

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.

Jentic One on Github View OpenAPI Document

Connect the M3O User Service API to your agent

Capabilities

Start building with M3O User Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

M3O User Service API