Install Jentic One Beta

Connect the PropelAuth API to your agent

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

Fetch user by ID

Update user

Delete user

Create user

Query users

Use Cases

Patterns agents use PropelAuth API for, with concrete tasks.

GET STARTED

Start building with PropelAuth API

Explore with Jentic One

View OpenAPI Document

Automated Users Management

Automate users operations by combining multiple PropelAuth API endpoints. Agents can update user and then delete user in a single workflow.

Call PUT /api/backend/v1/user/{user_id} to update user, then verify the result

AI Agent Integration via Jentic

AI agents discover and call PropelAuth 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 bearer tokens manually.

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

Key Endpoints

19 endpoints — propelauth is a b2b authentication service.

METHOD

PATH

DESCRIPTION

GET

/api/backend/v1/user/{user_id}

Fetch user by ID

PUT

/api/backend/v1/user/{user_id}

Update user

DELETE

/api/backend/v1/user/{user_id}

Delete user

GET

/api/backend/v1/user/email

Fetch user by email

GET

/api/backend/v1/user/username

Fetch user by username

POST

/api/backend/v1/user/

Create user

GET

/api/backend/v1/user/query

Query users

POST

/api/backend/v1/user/{user_id}/disable

Disable a user

GET

/api/backend/v1/user/{user_id}

Fetch user by ID

PUT

/api/backend/v1/user/{user_id}

Update user

DELETE

/api/backend/v1/user/{user_id}

Delete user

GET

/api/backend/v1/user/email

Fetch user by email

GET

/api/backend/v1/user/username

Fetch user by username

POST

/api/backend/v1/user/

Create user

GET

/api/backend/v1/user/query

Query users

POST

/api/backend/v1/user/{user_id}/disable

Disable a user

Why Jentic?

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

Setup

Wiring the PropelAuth API by hand means setting bearer auth, pointing requests at your own auth_url host, and managing user records yourself. Through Jentic you install once, import PropelAuth from the API Directory, store the token once, and your agent calls it.

Permission scoping

PropelAuth puts the user id in the URL path (/api/backend/v1/user/{user_id}), so a rule can pin your agent to acting on one user. You choose the operations it may call, so destructive ones like deleting or disabling a user are not included unless you add them.

Credential isolation

Your PropelAuth API 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 'fetch a user by id' or 'look up a user by email', and Jentic returns the matching PropelAuth operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using PropelAuth API through Jentic.

What authentication does the PropelAuth API use?

The PropelAuth API uses a Bearer token in the Authorization 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 fetch user by id with the PropelAuth API?

Yes. Use the GET /api/backend/v1/user/{user_id} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the PropelAuth 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 fetch user by id through Jentic?

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

How many endpoints does the PropelAuth API have?

The PropelAuth API exposes 19 endpoints covering users, organizations, magic links operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which PropelAuth operations and credentials the agent may use, so you can grant read calls like GET /api/backend/v1/user/{user_id} while withholding destructive ones such as deleting or disabling a user. PropelAuth also carries the user id in the URL path (/api/backend/v1/user/{user_id}), so a rule can pin the agent to acting on a single user rather than the whole directory. Nothing is callable unless you have added it to the operation set.

PropelAuth API

Name: PropelAuth API
Brand: PropelAuth API
Availability: InStock

AI ReadinessAI-Aware (B-)62/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthAuthenticationbearer19 EndpointsREST

For Agents

Programmatically fetch user by id, update user. Covers 19 operations with bearer authentication.

Use for: I need to fetch user by id, I want to user, Search for user, Find all fetch user by email

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

PropelAuth is a B2B authentication service. The backend API provides endpoints for managing users, organizations, API keys, and access tokens. Supports user creation, fetching, updating, role management, organization management, and magic link generation. The API exposes 19 endpoints secured with bearer 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

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

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

29%

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.

51%

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: B-Signals: 1

60%

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: BSignals: 1

66%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the PropelAuth API to your agent

Capabilities

Use Cases

Start building with PropelAuth API

Key Endpoints

Why Jentic?

Related APIs

FAQs

PropelAuth API

Jentic AI Readiness Score

PropelAuth 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