BE Identity

Name: BE Identity API
Brand: BE Identity
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthDirectory Servicesnone34 EndpointsREST

For Agents

Programmatically get all users repositories, get a single users repository. Covers 34 operations.

Connect the BE Identity to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BE Identity, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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 | sh

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 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 BE Identity API.

get all users repositories

create a users repository

update a users repository

delete a users repository

insert a user in a users repository for a defined application

GET STARTED

Start building with BE Identity API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use BE Identity API for, with concrete tasks.

★ Identity and Authentication Operations

Use the BE Identity to perform identity auth operations programmatically. The API provides 34 endpoints covering core functionality including get all users repositories, get a single users repository, create a users repository.

Call GET /repository/getall to get all users repositories

Automated repositories Management

Automate repositories operations by combining multiple BE Identity endpoints. Agents can get a single users repository and then create a users repository in a single workflow.

Call GET /repository/read to get a single users repository, then verify the result

AI Agent Integration via Jentic

AI agents discover and call BE Identity 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 none tokens manually.

Search Jentic for 'get all users repositories', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

34 endpoints — bookingexpert identity manager.

METHOD

PATH

DESCRIPTION

GET

/repository/getall

get all users repositories

GET

/repository/read

get a single users repository

GET

/repository/insert

create a users repository

GET

/repository/update

update a users repository

GET

/repository/delete

delete a users repository

GET

/user/insert

insert a user in a users repository for a defined application

GET

/user/delete

delete a user by his username for a defined application

GET

/user/login

check user credentials in a users repository for a defined application

GET

/repository/getall

get all users repositories

GET

/repository/read

get a single users repository

GET

/repository/insert

create a users repository

GET

/repository/update

update a users repository

GET

/repository/delete

delete a users repository

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

BE Identity none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'get all users repositories') and Jentic returns the matching BE Identity operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct BE Identity integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Auth0

Alternative identity auth API

Choose Auth0 when you need a different approach to identity auth operations

Alternative

Okta

Alternative identity auth API

Choose Okta when you need a different approach to identity auth operations

FAQs

Specific to using BE Identity API through Jentic.

What authentication does the BE Identity use?

The BE Identity uses no authentication. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I get all users repositories with the BE Identity?

Yes. Use the GET /repository/getall endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the BE Identity?

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 get all users repositories through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get all users repositories'. Jentic returns the matching BE Identity operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the BE Identity have?

The BE Identity exposes 34 endpoints covering repositories, users, recoveries operations.