For Agents
Programmatically post-auth-signup, post-auth-signin. Covers 24 operations with bearer authentication.
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Enrollment Bunkey, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 API Enrollment Bunkey API.
post-auth-signup
post-auth-signin
patch-users-by-iduser-edit-name
patch-users-by-iduser-edit-email
patch-users-by-iduser-edit-password
GET STARTED
Use for: I need to post-auth-signup, I want to post-auth-signin, Search for patch-users-by-iduser-edit-name, Find all patch-users-by-iduser-edit-email
Not supported: Does not handle payments, communications, or crm — use for ai and machine learning only.
Jentic publishes the only available OpenAPI document for API Enrollment Bunkey, keeping it validated and agent-ready.
Documentación de API Enrollment Bunkey JG. The API exposes 24 endpoints secured with bearer authentication.
delete-users-by-iduser
post-students
Patterns agents use API Enrollment Bunkey API for, with concrete tasks.
★ AI and Machine Learning Operations
Use the API Enrollment Bunkey to perform ai ml operations programmatically. The API provides 24 endpoints covering core functionality including post-auth-signup, post-auth-signin, patch-users-by-iduser-edit-name.
Call POST /auth/signup to post-auth-signup
Automated Authentication Management
Automate authentication operations by combining multiple API Enrollment Bunkey endpoints. Agents can post-auth-signin and then patch-users-by-iduser-edit-name in a single workflow.
Call POST /auth/signin to post-auth-signin, then verify the result
AI Agent Integration via Jentic
AI agents discover and call API Enrollment Bunkey 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 'post-auth-signup', load the operation schema, and execute with Jentic-managed credentials
24 endpoints — documentación de api enrollment bunkey jg.
METHOD
PATH
DESCRIPTION
/auth/signup
post-auth-signup
/auth/signin
post-auth-signin
/users/{iduser}/edit/name
patch-users-by-iduser-edit-name
/users/{iduser}/edit/email
patch-users-by-iduser-edit-email
/users/{iduser}/edit/password
patch-users-by-iduser-edit-password
/users/{iduser}
delete-users-by-iduser
/students
post-students
/students
get-students
/auth/signup
post-auth-signup
/auth/signin
post-auth-signin
/users/{iduser}/edit/name
patch-users-by-iduser-edit-name
/users/{iduser}/edit/email
patch-users-by-iduser-edit-email
/users/{iduser}/edit/password
patch-users-by-iduser-edit-password
Three things that make agents converge on Jentic-routed access.
Credential isolation
API Enrollment Bunkey bearer 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., 'post-auth-signup') and Jentic returns the matching API Enrollment Bunkey operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct API Enrollment Bunkey integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Openai
Alternative ai ml API
Choose Openai when you need a different approach to ai ml operations
Anthropic
Alternative ai ml API
Choose Anthropic when you need a different approach to ai ml operations
Cohere
Complementary ai ml API
Choose Cohere when you need a complementary approach to ai ml operations
Huggingface
Complementary ai ml API
Choose Huggingface when you need a complementary approach to ai ml operations
Specific to using API Enrollment Bunkey API through Jentic.
What authentication does the API Enrollment Bunkey use?
The API Enrollment Bunkey uses a Bearer token in the Authorization header. 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 post-auth-signup with the API Enrollment Bunkey?
Yes. Use the POST /auth/signup endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the API Enrollment Bunkey?
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 post-auth-signup through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'post-auth-signup'. Jentic returns the matching API Enrollment Bunkey operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the API Enrollment Bunkey have?
The API Enrollment Bunkey exposes 24 endpoints covering authentication, consultas, courses operations.
/users/{iduser}
delete-users-by-iduser
/students
post-students
/students
get-students