Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically bypasses authentication, adds profile. Covers 10 operations.
Use for: I need to bypasses authentication, I want to adds profile, Search for profile, Find all profile
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
This is a simple API. The API exposes 10 endpoints.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Examiners 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%2Fswaggerhub.bifrost-api%2Fswaggerhub-bifrost-api" | 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.bifrost-api%2Fswaggerhub-bifrost-api" | 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 Examiners API.
bypasses authentication
adds profile
get profile
update profile
removes token
registers token
count all alerts
Patterns agents use Examiners API for, with concrete tasks.
★ Developer Tools Operations
Use the Examiners API to perform developer tools operations programmatically. The API provides 10 endpoints covering core functionality including bypasses authentication, adds profile, get profile.
Call POST /examiner/authenticate/bypass to bypasses authentication
Automated profile Management
Automate profile operations by combining multiple Examiners API endpoints. Agents can adds profile and then get profile in a single workflow.
Call POST /examiner/profile/add to adds profile, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Examiners 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 none tokens manually.
Search Jentic for 'bypasses authentication', load the operation schema, and execute with Jentic-managed credentials
10 endpoints — this is a simple api.
METHOD
PATH
DESCRIPTION
/examiner/authenticate/bypass
bypasses authentication
/examiner/profile/add
adds profile
/examiner/profile/get
get profile
/examiner/profile/update
update profile
/examiner/notifications/remove
removes token
/examiner/notifications/register
registers token
/examiner/alerts/count
count all alerts
/examiner/alerts
post a new alert
/examiner/authenticate/bypass
bypasses authentication
/examiner/profile/add
adds profile
/examiner/profile/get
get profile
/examiner/profile/update
update profile
/examiner/notifications/remove
removes token
/examiner/notifications/register
registers token
/examiner/alerts/count
count all alerts
/examiner/alerts
post a new alert
What agents get from Jentic-routed access to this vendor.
Setup
This Examiners API is published as a SwaggerHub mock with no authentication, so wiring it by hand still means pointing at the virtual host and coding your own request bodies, response parsing, and retries. Through Jentic you install once, import the Examiners API from the API Directory, and your agent calls it directly.
Permission scoping
This API selects examiner records through values in the request body rather than a resource id in the URL path, so scope by operation: limit the agent to the operations it needs, such as reading a profile or counting alerts, and leave writes like adding or updating a profile out unless you add them.
Credential isolation
This API declares no authentication, so there is no secret to hand the agent. If you point it at a protected deployment, the credential is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'get an examiner profile' or 'count alerts', and Jentic returns the matching Examiners API 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 Examiners API through Jentic.
What authentication does the Examiners API use?
The Examiners API uses no authentication. 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 bypasses authentication with the Examiners API?
Yes. Use the POST /examiner/authenticate/bypass endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Examiners 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 bypasses authentication through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'bypasses authentication'. Jentic returns the matching Examiners API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Examiners API have?
The Examiners API exposes 10 endpoints covering profile, notifications, alerts operations.
Can I limit what my agent is allowed to do with the Examiners API?
Yes. Because you run Jentic One yourself and set the rules, you decide which Examiners API operations the agent may call and which credentials it may use. Since this API selects examiner records through values in the request body rather than an id in the URL, you scope by operation: allow read-only calls like GET /examiner/profile/get and GET /examiner/alerts/count while withholding writes such as POST /examiner/profile/add or POST /examiner/profile/update. The agent can only invoke the operations you grant, so it cannot register tokens or post alerts unless you enable those.
GET STARTED