Install Jentic One Beta

Connect the SimpleLogin API to your agent

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

User authentication

Two-factor authentication

Confirm new account with activation code

Request password reset

GET STARTED

Start building with SimpleLogin API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use SimpleLogin API for, with concrete tasks.

★ CRM Operations

Use the SimpleLogin API to perform crm operations programmatically. The API provides 25 endpoints covering core functionality including user authentication, two-factor authentication, register a new account.

Call POST /api/auth/login to user authentication

Automated Alias Management

Automate alias operations by combining multiple SimpleLogin API endpoints. Agents can two-factor authentication and then register a new account in a single workflow.

Call POST /api/auth/mfa to two-factor authentication, then verify the result

AI Agent Integration via Jentic

AI agents discover and call SimpleLogin API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'user authentication', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

25 endpoints — api for simplelogin email alias service.

METHOD

PATH

DESCRIPTION

POST

/api/auth/login

User authentication

POST

/api/auth/mfa

Two-factor authentication

POST

/api/auth/register

POST

/api/auth/activate

Confirm new account with activation code

POST

/api/auth/forgot_password

Request password reset

GET

/api/user_info

Get current user information

PATCH

/api/user_info

Update user profile

GET

/api/stats

Get user statistics

POST

/api/auth/login

User authentication

POST

/api/auth/mfa

Two-factor authentication

POST

/api/auth/register

POST

/api/auth/activate

Confirm new account with activation code

POST

/api/auth/forgot_password

Request password reset

GET

/api/user_info

Get current user information

PATCH

/api/user_info

Update user profile

GET

/api/stats

Get user statistics

Why Jentic?

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

Setup

Wiring SimpleLogin by hand means learning that its key goes in a non-standard Authentication header and carrying it across the login, MFA, and user-info calls yourself. Through Jentic you install once, import SimpleLogin from the API Directory, store the key once, and your agent calls it.

Permission scoping

SimpleLogin identifies the caller by the account behind the key rather than a resource id in the URL path, so scope the agent by operations: limit it to the operations it needs, such as reading user info or account stats, and leave out account changes like updating user settings unless you add them.

Credential isolation

Your SimpleLogin API 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 'log a user in' or 'read account stats', and Jentic returns the matching SimpleLogin operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using SimpleLogin API through Jentic.

What authentication does the SimpleLogin API use?

The SimpleLogin API uses an API key passed in the `Authentication` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I user authentication with the SimpleLogin API?

Yes. Use the POST /api/auth/login endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the SimpleLogin API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I user authentication through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'user authentication'. Jentic returns the matching SimpleLogin API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the SimpleLogin API have?

The SimpleLogin API exposes 25 endpoints covering alias, aliases, api_key operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which SimpleLogin operations and credentials the agent can use. Because SimpleLogin identifies the caller by the account behind the API key rather than a resource id in the URL, you scope the agent by operation: allow only what it needs, such as reading user info (GET /api/user_info) or account stats (GET /api/stats), and leave out account changes like updating user settings unless you add them. The stored key is injected at execution time, so the agent can call only the operations you permit.

SimpleLogin API

Name: SimpleLogin API
Brand: SimpleLogin API
Availability: InStock

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyCRMContact ManagementapiKey25 EndpointsREST

For Agents

Programmatically user authentication, two-factor authentication. Covers 25 operations with apiKey authentication.

Use for: I need to user authentication, I want to two-factor authentication, Search for register a new account, Find all confirm new account with activation code

Not supported: Does not handle payments, communications, or developer tools - use for crm only.

API for SimpleLogin email alias service. Provides endpoints for authentication, managing email aliases, mailboxes, contacts, custom domains, and user settings. The API exposes 25 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

34%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

88%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1

56%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the SimpleLogin API to your agent

Capabilities

Start building with SimpleLogin API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

SimpleLogin API

Jentic AI Readiness Score

SimpleLogin API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness