canonical: https://jentic.com/apis/userfront.com/userfront

# Userfront API

Userfront is a user authentication and identity management platform. The server-to-server API provides user management, tenant management, role management, and authentication token operations. The API exposes 14 endpoints secured with bearer authentication.

## For AI agents

Programmatically create a user, list users. Covers 14 operations with bearer authentication.

## Scope

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

## Capabilities

- Create a user
- List users
- Get a user
- Update a user
- Delete a user
- Set user roles

## Use cases

### Identity and Authentication Operations

Use the Userfront API to perform identity auth operations programmatically. The API provides 14 endpoints covering core functionality including create a user, list users, get a user.

Example prompt: Call POST `/v0/users` to create a user

### Automated Authentication Management

Automate authentication operations by combining multiple Userfront API endpoints. Agents can list users and then get a user in a single workflow.

Example prompt: Call GET `/v0/users` to list users, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Userfront 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.

Example prompt: Search Jentic for 'create a user', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v0/users` | Create a user |
| GET | `/v0/users` | List users |
| GET | `/v0/users/{userId}` | Get a user |
| PUT | `/v0/users/{userId}` | Update a user |
| DELETE | `/v0/users/{userId}` | Delete a user |
| GET | `/v0/users/{userId}/roles` | Get user roles |
| PUT | `/v0/users/{userId}/roles` | Set user roles |
| GET | `/v0/tenants/{tenantId}` | Get tenant information |

## Key resources

- **Authentication** — Operations related to Authentication
- **Roles** — Operations related to Roles
- **Tenants** — Operations related to Tenants
- **Users** — Operations related to Users

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 81 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 68 / 100
- **View full report:** https://jentic.com/apis/userfront.com/userfront/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Userfront API by hand means attaching its bearer token and moving between user, role, and tenant endpoints yourself. Through Jentic you install once, import Userfront from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Userfront puts the user id in the URL path (`/v0/users/{userId}`), so a rule can pin your agent to one user: it can read that user and their roles if you allow it. You choose the operations it may call, so destructive ones like user deletion are not included unless you add them.
- **Credential handling:** Your Userfront 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 'create a user' or 'read a user's roles', and Jentic returns the matching Userfront operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the Userfront API use?

The Userfront 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 create a user with the Userfront API?

Yes. Use the POST `/v0/users` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Userfront 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 create a user through Jentic?

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

### How many endpoints does the Userfront API have?

The Userfront API exposes 14 endpoints covering authentication, roles, tenants operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Userfront operations and credentials the agent may use. Because Userfront puts the user id in the URL path (`/v0/users/{userId}`), a rule can pin the agent to a single user, letting it read that user and their roles while blocking others. You choose the operations it may call, so destructive ones like DELETE `/v0/users/{userId}` are excluded unless you explicitly add them.