Install Jentic One Beta

Connect the LoginRadius API to your agent

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

Authenticate users via POST /identity/v2/auth/login and issue an access token

Validate or invalidate an access token through /identity/v2/auth/access_token endpoints

Initiate forgot-password and reset-password flows on /identity/v2/auth/password

GET STARTED

Start building with LoginRadius API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use LoginRadius API for, with concrete tasks.

★ Email and Password Registration Flow

Register new users from a sign-up form via POST /identity/v2/auth/register and trigger an email verification with the spec's email-verify flow. The same payload accepts custom profile fields so onboarding metadata is captured at sign-up.

POST /identity/v2/auth/register with email='jane@example.com', password='S3cure!', and FirstName='Jane' to create the account.

Token-based Login for SPAs

Authenticate single-page applications by calling POST /identity/v2/auth/login and storing the returned access token client-side. Each subsequent request validates the token via GET /identity/v2/auth/access_token/validate so backends can trust the bearer.

POST /identity/v2/auth/login with email and password, then call GET /identity/v2/auth/access_token/validate with the returned token.

Self-service Password Reset

Allow users to recover access by initiating POST /identity/v2/auth/password/forgot, which emails a reset link, then completing PUT /identity/v2/auth/password/reset with the token and new password. This avoids manual support tickets for forgotten credentials.

POST /identity/v2/auth/password/forgot with email='jane@example.com' to send the reset email.

Role-based Access Control Setup

Provision roles for a new application by calling POST /identity/v2/manage/role and listing them with GET /identity/v2/manage/role. Roles can later be attached to users via the manage account endpoints to enforce scoped access.

POST /identity/v2/manage/role with body Name='editor' to create the role.

AI Agent User Provisioning via Jentic

An agent that handles HR onboarding can register new employee accounts in LoginRadius and assign them a starter role through Jentic. The API key stays in the vault so the agent never sees the secret.

Through Jentic, search 'register a new user', load the LoginRadius POST /identity/v2/auth/register operation, and execute it with the new hire's email.

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for loginradius api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/identity/v2/auth/register

POST

/identity/v2/auth/login

Authenticate with email and password

GET

/identity/v2/auth/access_token/validate

Validate an access token

POST

/identity/v2/auth/password/forgot

Trigger forgot-password email

PUT

/identity/v2/auth/password/reset

Reset password with token

GET

/identity/v2/manage/account/{uid}

Look up an account by uid

POST

/identity/v2/manage/role

Create a new role

POST

/identity/v2/auth/register

POST

/identity/v2/auth/login

Authenticate with email and password

GET

/identity/v2/auth/access_token/validate

Validate an access token

POST

/identity/v2/auth/password/forgot

Trigger forgot-password email

PUT

/identity/v2/auth/password/reset

Reset password with token

GET

/identity/v2/manage/account/{uid}

Look up an account by uid

POST

/identity/v2/manage/role

Create a new role

Why Jentic?

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

Setup

Wiring the LoginRadius API by hand means setting up its X-API-Key header, managing the apikey and apisecret pair, and shaping registration, login, and account management request bodies against api.loginradius.com yourself. Through Jentic you install once, import LoginRadius from the API Directory, store the key once, and your agent calls it.

Permission scoping

LoginRadius carries the target through request bodies and query parameters for its auth flows, so scoping is by operation: limit the agent to the operations it needs, such as registering a user or starting a password reset, and leave out account management or role administration if the agent only handles sign-up.

Credential isolation

Your LoginRadius apikey and apisecret are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'register a user' or 'reset a password', and Jentic returns the matching LoginRadius operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using LoginRadius API through Jentic.

Why is there no official OpenAPI spec for LoginRadius API?

LoginRadius does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call LoginRadius API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the LoginRadius API use?

LoginRadius uses an API key passed as a query parameter (apikey). Manage endpoints additionally require an apisecret. Through Jentic both values are stored encrypted in the vault and injected at execution, never reaching the agent's context.

Can I implement self-service password reset with the LoginRadius API?

Yes. Call POST /identity/v2/auth/password/forgot to email the user a reset link, then complete the flow with PUT /identity/v2/auth/password/reset using the token from the email.

How do I register a new user through Jentic?

Run `pip install jentic`, search Jentic for 'register a new user', load the LoginRadius POST /identity/v2/auth/register operation, and execute it with the user's email and password. Jentic returns the new uid.

What are the rate limits for the LoginRadius API?

Rate limits depend on your LoginRadius plan tier. The spec does not embed specific numbers. Implement exponential backoff on HTTP 429 responses to stay within quota.

Can I manage user roles via the LoginRadius API?

Yes. Use POST /identity/v2/manage/role to create roles, GET /identity/v2/manage/role to list them, and DELETE /identity/v2/manage/role/{roleName} to remove a role.

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

Yes. Because you run Jentic One yourself, your own rules decide which LoginRadius operations and credentials the agent may use, and LoginRadius scopes by operation since the target is carried in each request body and query parameter. If your agent only handles sign-up, you can allow just the register and password-reset operations, such as POST /identity/v2/auth/register and POST /identity/v2/auth/password/forgot, and leave out account management and role administration like GET /identity/v2/manage/account/{uid} and POST /identity/v2/manage/role. Your apikey and apisecret stay stored by your own instance and are injected at execution, so the agent only ever exercises the operations you permit.

LoginRadius API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Agent-ready OpenAPI document · curated by JenticIdentity AuthAuthenticationapiKey18 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Register users, authenticate with email and password, manage profiles and access tokens, and administer roles and accounts in LoginRadius CIAM.

Use for: Register a new user with email and password, Authenticate a user and return an access token, Validate the access token attached to this request, Reset the password for a user who forgot theirs

Not supported: Does not handle SSO federation configuration, MFA enrolment beyond basic flows, or organisation/tenant directory structures - use for end-user authentication, profile management, and role administration only.

Jentic publishes the only available OpenAPI specification for LoginRadius API, keeping it validated and agent-ready. LoginRadius is a customer identity and access management (CIAM) platform that exposes registration, login, password recovery, profile management, email verification, role management, and account administration operations. The spec covers 18 endpoints across the auth and manage namespaces, supporting both end-user flows (register, login, change password) and back-office tasks (look up account by uid, manage roles).

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

98%

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).

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: C-Signals: 4

57%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

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

55%

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).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the LoginRadius API to your agent

Capabilities

Start building with LoginRadius API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

LoginRadius API

Jentic AI Readiness Score

LoginRadius 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