Install Jentic One Beta
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.
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%2Fswaggerhub.jgutierrez1457%2Fapi-enrollment-bunkey" | shStep 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%2Fswaggerhub.jgutierrez1457%2Fapi-enrollment-bunkey" | 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
GET STARTED
For Agents
Programmatically post-auth-signup, post-auth-signin. Covers 24 operations with bearer authentication.
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.
Documentación de API Enrollment Bunkey JG. The API exposes 24 endpoints secured with bearer authentication.
patch-users-by-iduser-edit-password
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
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the API Enrollment Bunkey by hand means implementing its JWT bearer flow, pointing at the Heroku host, and writing your own retry handling around the users, students, courses, and enrollments calls. Through Jentic you install once, import API Enrollment Bunkey from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
This API puts the resource id in the URL path (/users/{iduser}, /students/{idstudent}, /courses/{idcourse}, /enrollments/{idenrollment}), so a rule can pin your agent to one course or enrollment and the operations around it. You choose the operations it may call, so destructive ones like deleting a user or removing a student from an enrollment are not included unless you add them.
Credential isolation
Your API Enrollment Bunkey bearer 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 'enroll a student in a course' or 'look up an enrollment', and Jentic returns the matching API Enrollment Bunkey operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.
Can I limit what my agent is allowed to do with the API Enrollment Bunkey?
Yes. Because you run Jentic One yourself, your own rules decide which API Enrollment Bunkey operations and credentials the agent may use, so you can grant read-only calls like listing students or looking up an enrollment while withholding destructive ones such as deleting a user or removing a student from an enrollment. Since this API carries the resource id in the URL path, for example /users/{iduser}, /students/{idstudent}, /courses/{idcourse}, and /enrollments/{idenrollment}, you can pin the agent to a single course or enrollment and just the operations around it. Any operation you do not add stays off limits.
/users/{iduser}
delete-users-by-iduser
/students
post-students
/students
get-students