Install Jentic One Beta

Connect the MyDeepTalk API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MyDeepTalk 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%2Fmydeeptalk.com%2Fmydeeptalk" | 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%2Fmydeeptalk.com%2Fmydeeptalk" | 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 MyDeepTalk API.

Authenticate a user and obtain a bearer access token

Retrieve the profile of the currently logged-in user

Check server availability with a health-check request

Use Cases

Patterns agents use MyDeepTalk API for, with concrete tasks.

GET STARTED

Start building with MyDeepTalk API

Explore with Jentic One

View OpenAPI Document

★ Agent-Driven User Onboarding

An AI agent onboards a new user by registering them and then logging them in through Jentic. The signup operation creates the account from an email and password, and the login operation returns a bearer token the agent reuses on later authenticated requests, so the whole sign-up-then-sign-in flow runs without hand-wired auth code.

Register a new user by posting an email and password to the signup operation, then call the login operation and store the returned bearer token for later requests.

Session Validation

A service confirms that a stored bearer token is still valid and identifies who it belongs to. The current-user operation returns the profile of the authenticated caller, so the agent can verify a session and personalize responses before continuing.

Send the stored bearer token to the current-user operation and confirm the session by reading the returned profile.

Availability Monitoring

An uptime monitor or agent checks that the authentication service is reachable before attempting a login. The health-check operation responds without any credential, making it a cheap readiness probe ahead of signup or login traffic.

Call the health-check operation and treat a successful response as a signal that signup and login are ready to use.

Key Endpoints

4 endpoints — the mydeeptalk api registers new users and authenticates them with email and password, returning a bearer token your application can reuse on later requests.

METHOD

PATH

DESCRIPTION

POST

/auth/signup

POST

/auth/login

Authenticate and obtain an access token

GET

/users/me

Get the current logged-in user

GET

/ping

Server health check

POST

/auth/signup

POST

/auth/login

Authenticate and obtain an access token

GET

/users/me

Get the current logged-in user

GET

/ping

Server health check

Why Jentic?

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

Setup

Wiring the MyDeepTalk API by hand means implementing its signup and login calls, capturing the returned bearer JWT, and attaching it to every authenticated request yourself. Through Jentic you install once, import it from the API Directory, store the token once, and your agent calls it.

Permission scoping

The API's operations are the unit a rule bounds, so you can pin your agent to the ones you pick, such as login and reading the current user. You choose the operations it may call, so signup or other calls are not included unless you add them.

Credential isolation

Your MyDeepTalk bearer token 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 'log in a user' or 'get the current user', and Jentic returns the matching MyDeepTalk operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using MyDeepTalk API through Jentic.

What authentication does the MyDeepTalk API use?

The MyDeepTalk API authenticates with a bearer token in JSON Web Token (JWT) format per its OpenAPI spec. Your agent obtains the token from the login operation and sends it on authenticated requests such as reading the current user, while the health-check operation is open. Through Jentic the token is stored encrypted in your own Jentic One instance and injected at call time.

Can I register and log in users with the MyDeepTalk API?

Yes. The API provides a signup operation to register a new user with an email and password and a login operation that returns a bearer access token. A separate operation returns the profile of the currently authenticated user.

What are the rate limits for the MyDeepTalk API?

The OpenAPI spec does not specify rate limits. Check the MyDeepTalk documentation at https://mydeeptalk.com for current limits before running high-volume signup or login traffic.

How do I log in a MyDeepTalk user through Jentic?

Search Jentic for 'log in a user and get an access token', add the MyDeepTalk API from the directory, and your agent calls the login operation, then reuses the returned bearer token on later requests. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a MyDeepTalk API MCP server?

You don't need an MCP server to give your agent the MyDeepTalk API. Jentic connects it directly from the API Directory: import it, store the login token once, and your agent calls the authentication operations. Nothing extra loads into the agent's context until a call is made.

Can I limit what my agent is allowed to do with the MyDeepTalk API?

Yes. Write a rule that allows just the operations the agent needs, such as login and reading the current user, so it cannot call signup or anything else, and every call is logged. MyDeepTalk carries user details in the request body, so rules bound which operations your agent may call.

MyDeepTalk API

Name: MyDeepTalk API
Brand: MyDeepTalk API
Availability: InStock

Community OpenAPI document · agent-readyIdentity AuthAuthenticationbearer4 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Register and log in MyDeepTalk users with email and password, receive a bearer access token, and read the profile of the currently authenticated user.

Use for: Register a new MyDeepTalk user, Log in and get an access token, Get the current logged-in user's profile, Check whether the MyDeepTalk API is available

Not supported: Does not handle messaging, payments, or content storage. Use for user signup and authentication only.

The MyDeepTalk API registers new users and authenticates them with email and password, returning a bearer token your application can reuse on later requests. It also exposes the profile of the currently logged-in user and a lightweight health-check operation for monitoring availability.

Jentic One on Github View OpenAPI Document

Connect the MyDeepTalk API to your agent

Capabilities

Use Cases

Start building with MyDeepTalk API

Key Endpoints

Why Jentic?

Related APIs

FAQs

MyDeepTalk API