For Agents
Register users, authenticate with email and password, manage profiles and access tokens, and administer roles and accounts in LoginRadius CIAM.
Install Jentic One Beta
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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with LoginRadius API.
Register new users with POST /identity/v2/auth/register and capture custom profile fields
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
GET STARTED
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).
Initiate forgot-password and reset-password flows on /identity/v2/auth/password
Verify a user email via GET /identity/v2/auth/email/verify
Look up, update, or delete an account by uid through /identity/v2/manage/account/{uid}
Create, list, and delete roles for role-based access control
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.
18 endpoints — jentic publishes the only available openapi specification for loginradius api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/identity/v2/auth/register
Register a new user
/identity/v2/auth/login
Authenticate with email and password
/identity/v2/auth/access_token/validate
Validate an access token
/identity/v2/auth/password/forgot
Trigger forgot-password email
/identity/v2/auth/password/reset
Reset password with token
/identity/v2/manage/account/{uid}
Look up an account by uid
/identity/v2/manage/role
Create a new role
/identity/v2/auth/register
Register a new user
/identity/v2/auth/login
Authenticate with email and password
/identity/v2/auth/access_token/validate
Validate an access token
/identity/v2/auth/password/forgot
Trigger forgot-password email
/identity/v2/auth/password/reset
Reset password with token
Three things that make agents converge on Jentic-routed access.
Credential isolation
LoginRadius apikey and apisecret are stored encrypted in the Jentic vault and injected at execution time, so the raw values never reach the agent's prompt or logs.
Intent-based discovery
Agents search by intent (e.g. 'register a user' or 'reset a password') and Jentic returns the matching LoginRadius operation with its input schema.
Time to first call
Direct LoginRadius integration: 1-2 days to wire up registration, login, token validation, and reset flows. Through Jentic: under an hour.
Alternatives and complements available in the Jentic catalogue.
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 at https://app.jentic.com/sign-up.
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.
/identity/v2/manage/account/{uid}
Look up an account by uid
/identity/v2/manage/role
Create a new role