canonical: https://jentic.com/apis/mydeeptalk.com/mydeeptalk # MyDeepTalk API 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. ## For AI 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. ## Scope Does not handle messaging, payments, or content storage. Use for user signup and authentication only. ## Capabilities - Register a new user with an email and password - 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 ### 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. Example prompt: 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. Example prompt: 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. Example prompt: Call the health-check operation and treat a successful response as a signal that signup and login are ready to use. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/auth/signup` | Register a new user | | POST | `/auth/login` | Authenticate and obtain an access token | | GET | `/users/me` | Get the current logged-in user | | GET | `/ping` | Server health check | ## Key resources - **Authentication** — Register a user and exchange email and password for a bearer access token - **Users** — Read the profile of the currently authenticated user - **Health** — Check that the service is reachable ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Auth0** — Full identity platform with signup, login, MFA, and social connections. - **Stytch** — Authentication API for passwords, magic links, and passwordless flows. - **Supabase** — Backend platform pairing user authentication with a hosted Postgres database. ## FAQ ### 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.