Install Jentic One Beta

Connect the User Manager API to your agent

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

List a site's users with filters such as has_private_charge_point, can_use_public_charge_point, and joined_reason

Grant or revoke a site user's public charge point access with can_use_public_charge_point

Invite site administrators with email and role_id, and resend or cancel their invitations

Create, update, and remove operators with role_id and site_ids, and resend or cancel operator invitations

GET STARTED

Start building with User Manager API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use User Manager API for, with concrete tasks.

★ Site access admin agent through Jentic

A site manager's agent handles access requests for a charging location. It searches Jentic for 'list users at a charging site', receives the site users operation schema, and lists users at one site_id filtered by can_use_public_charge_point. When a request comes in it calls the site user update with can_use_public_charge_point set to true or false, so access changes are made without opening the admin backend.

Call GET /web/admin_backend/sites/{site_id}/users with site_id=12 and can_use_public_charge_point=false, then PATCH /web/admin_backend/sites/{site_id}/users/{user_id} with can_use_public_charge_point=true for the requested user

Administrator and operator onboarding

New staff need the right role at the right site. POST /web/admin_backend/sites/{site_id}/administrators invites an administrator with email and role_id, and POST /web/operator_panel/operators invites an operator with email, role_id, and site_ids. Both have invitation resend and cancel operations, and GET /web/roles lists the roles and permissions to choose from.

Call GET /web/roles to find the role_id for 'site manager', then POST /web/admin_backend/sites/{site_id}/administrators with email='lee@example.com' and that role_id

Driver self-service profile updates

EV drivers using the NexaGrids app can keep their details current. PATCH /web/info updates fields such as first_name, phone_number, address, car_brand, and car_number, PATCH /web/change_password sets a new password, and GET /web/deletion_check reports whether the account can be deleted before DELETE /web/self is called.

Call PATCH /web/info with car_brand='Tesla' and car_number='ABC-1234', then GET /web/info to confirm the change

Key Endpoints

89 endpoints — the nexagrids user manager api manages the users, administrators, operators, roles, and sites behind the nexagrids ev charging platform.

METHOD

PATH

DESCRIPTION

GET

/web/admin_backend/sites/{site_id}/users

List a site's users

PATCH

/web/admin_backend/sites/{site_id}/users/{user_id}

Update a site user's public charge point access

POST

/web/admin_backend/sites/{site_id}/administrators

Invite a site administrator

GET

/web/operator_panel/operators

List operators

POST

/web/operator_panel/operators

Create an operator

GET

/web/roles

List roles and permissions

PATCH

/web/info

Update the app user's profile

GET

/web/admin_backend/sites/{site_id}/users

List a site's users

PATCH

/web/admin_backend/sites/{site_id}/users/{user_id}

Update a site user's public charge point access

POST

/web/admin_backend/sites/{site_id}/administrators

Invite a site administrator

GET

/web/operator_panel/operators

List operators

POST

/web/operator_panel/operators

Create an operator

GET

/web/roles

List roles and permissions

PATCH

/web/info

Update the app user's profile

Why Jentic?

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

Setup

Wiring NexaGrids by hand means obtaining a JWT, reading Chinese-language summaries to tell the web, public, internal, and Auth0 routes apart, and unwrapping the meta and data envelope on every call. Through Jentic you install once, import NexaGrids from the API Directory, store the JWT once, and your agent calls it.

Permission scoping

NexaGrids puts the site id in the URL path (/web/admin_backend/sites/{site_id}/...), so a rule can pin your agent to one site and the operations you pick. You choose the operations it may call, so destructive ones like DELETE /web/self or the /internal deletes are not included unless you add them.

Credential isolation

Your NexaGrids JWT 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 'list users at a charging site' or 'invite an operator', and Jentic returns the matching NexaGrids operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using User Manager API through Jentic.

What authentication does the NexaGrids User Manager API use?

Per its OpenAPI spec, the NexaGrids User Manager API declares a bearer JWT (`BearerAuth`) sent in the Authorization header. The spec's tags describe the /web routes as JWT-authenticated, the /public routes as needing no authentication, and the /internal routes as service-to-service. Through Jentic, the JWT is stored encrypted by your own Jentic One instance and injected at call time.

Can I control who uses public charge points at a site with the NexaGrids User Manager API?

Yes. PATCH /web/admin_backend/sites/{site_id}/users/{user_id} takes can_use_public_charge_point as a required boolean, and GET /web/admin_backend/sites/{site_id}/users filters a site's users by that same flag and by has_private_charge_point.

What are the rate limits for the NexaGrids User Manager API?

The OpenAPI spec does not specify rate limits. Check https://nexagrids.dev or contact NexaGrids for current limits.

How do I invite a site administrator with the NexaGrids User Manager API through Jentic?

Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, add NexaGrids from the Jentic API Directory, and store your JWT. Your agent searches for 'invite a site administrator', reads role IDs from GET /web/roles, and calls POST /web/admin_backend/sites/{site_id}/administrators with email and role_id. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the NexaGrids User Manager API?

Yes. Write a rule that allows only GET and PATCH on /web/admin_backend/sites/12/users and its user paths. The agent can then review site 12's users and switch their public charging access, but it cannot invite administrators, touch other sites, or reach the /internal routes, and each call is logged.

Is there a NexaGrids MCP server?

You don't need an MCP server to give your agent the NexaGrids User Manager API. Jentic connects it directly from the API Directory: import it, store your JWT once, and your agent calls it.

What does the NexaGrids response envelope look like?

Every response wraps its payload as meta plus data. On success meta.code is 0 and meta.message is success; on error data is null and meta.code carries the error code, such as 100004 for user not found.

Nexagrids User Manager API

AI ReadinessFoundational (D+)47/100

See full scorecard

Community OpenAPI document · agent-readyIdentity AuthDirectory Servicesbearer89 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

List and update NexaGrids site users and their public charge point access, invite and manage site administrators and operators, read roles and permissions, and maintain user profiles.

Use for: I need to list all users at site 12 who can use public charge points, Revoke public charging access for one user at a site, Invite a new site administrator with the manager role, Resend the invitation to an operator who has not joined yet

Not supported: Does not control chargers, start charging sessions, process payments, or issue login tokens. Use for managing NexaGrids users, administrators, operators, roles, and site access only.

The NexaGrids User Manager API manages the users, administrators, operators, roles, and sites behind the NexaGrids EV charging platform. Its web endpoints let an app user read and update their profile, including car_brand and car_number, change their password, or check whether their account can be deleted, and they let site administrators list a site's users, add a user to a site, and grant or revoke public charge point access. Operator panel endpoints invite, update, and remove operators across sites, while internal service routes cover operator companies, contacts, site assignments, delegations, and Auth0 login and registration triggers. Every response uses a meta and data envelope, with meta.code set to 0 on success.

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.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

14%

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

11%

Example Density

How richly the API is illustrated with examples.

30%

Example Validity

Percentage of examples that conform to their schemas.

71%

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: FSignals: 4

28%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

70%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

87%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

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

52%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the User Manager API to your agent

Capabilities

Start building with User Manager API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Nexagrids User Manager API

Jentic AI Readiness Score

User Manager 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