Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SlideRoom API V2, 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%2Fslideroom.com%2Fslideroom" | 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%2Fslideroom.com%2Fslideroom" | 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 SlideRoom API V2 API.
Updates the custom attributes for an applicant.
Gets the custom attributes for an applicant.
Deletes a custom attribute for an applicant.
Requests the generation of application export files (tabular, pdf, zip).
Monitor SlideRoom API V2 operational status and events
GET STARTED
Patterns agents use SlideRoom API V2 API for, with concrete tasks.
★ Developer Tools Operations
Use the SlideRoom API V2 to perform developer tools operations programmatically. The API provides 11 endpoints covering core functionality including updates the custom attributes for an applicant., gets the custom attributes for an applicant., deletes a custom attribute for an applicant..
Call POST /api/v2/applicant/attributes to updates the custom attributes for an applicant.
Automated Applicant Management
Automate applicant operations by combining multiple SlideRoom API V2 endpoints. Agents can gets the custom attributes for an applicant. and then deletes a custom attribute for an applicant. in a single workflow.
Call GET /api/v2/applicant/attributes to gets the custom attributes for an applicant., then verify the result
AI Agent Integration via Jentic
AI agents discover and call SlideRoom API V2 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 'updates the custom attributes for an applicant.', load the operation schema, and execute with Jentic-managed credentials
11 endpoints — slideroom.
METHOD
PATH
DESCRIPTION
/api/v2/applicant/attributes
Updates the custom attributes for an applicant.
/api/v2/applicant/attributes
Gets the custom attributes for an applicant.
/api/v2/applicant/attributes
Deletes a custom attribute for an applicant.
/api/v2/applicant/attributes/names
Gets the custom applicant attributes used by the organization.
/api/v2/application/attributes/names
Gets the custom application attributes used by the organization.
/api/v2/application/request-export
Requests the generation of application export files (tabular, pdf, zip).
/api/v2/application/{applicationId}/attributes
Updates the custom attributes for an application. API Import is available in the
/api/v2/application/{applicationId}/attributes
Gets the custom attributes for an application.
/api/v2/applicant/attributes
Updates the custom attributes for an applicant.
/api/v2/applicant/attributes
Gets the custom attributes for an applicant.
/api/v2/applicant/attributes
Deletes a custom attribute for an applicant.
/api/v2/applicant/attributes/names
Gets the custom applicant attributes used by the organization.
/api/v2/application/attributes/names
Gets the custom application attributes used by the organization.
/api/v2/application/request-export
Requests the generation of application export files (tabular, pdf, zip).
/api/v2/application/{applicationId}/attributes
Updates the custom attributes for an application. API Import is available in the
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SlideRoom API V2 by hand means targeting api.slideroom.com and shaping each applicant and application attribute call yourself. Through Jentic you install once, import SlideRoom from the API Directory, and your agent calls it.
Permission scoping
SlideRoom puts the application id in the URL path (/api/v2/application/{applicationId}/attributes), so a rule can pin your agent to a specific application's attribute operations. You choose the operations it may call, so destructive ones like deleting applicant attributes are not included unless you add them.
Credential isolation
Any access SlideRoom requires is held once by your own Jentic One instance and applied at execution time rather than by the agent. Nothing sensitive enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'read application attributes' or 'request an application export', and Jentic returns the matching SlideRoom 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 SlideRoom API V2 API through Jentic.
What authentication does the SlideRoom API V2 use?
The SlideRoom API V2 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 updates the custom attributes for an applicant. with the SlideRoom API V2?
Yes. Use the POST /api/v2/applicant/attributes endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SlideRoom API V2?
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 updates the custom attributes for an applicant. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'updates the custom attributes for an applicant.'. Jentic returns the matching SlideRoom API V2 operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SlideRoom API V2 have?
The SlideRoom API V2 exposes 11 endpoints covering applicant, application, export operations.
Can I limit what my agent is allowed to do with the SlideRoom API V2?
Yes. Because Jentic One is self-hosted, your own rules decide which SlideRoom operations and credentials the agent may use. You pick the exact endpoints it can call, so read operations like GET /api/v2/applicant/attributes can be permitted while destructive ones like deleting applicant attributes stay off unless you add them. Since SlideRoom carries the application id in the URL path, such as /api/v2/application/{applicationId}/attributes, you can also pin the agent to a specific application's attribute operations.
For Agents
Programmatically updates the custom attributes for an applicant., gets the custom attributes for an applicant.. Covers 11 operations.
Use for: I need to updates the custom attributes for an applicant., I want to gets the custom attributes for an applicant., Search for deletes a custom attribute for an applicant., Find all gets the custom applicant attributes used by the organization.
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
slideroom.com/main version v2. The API exposes 11 endpoints.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
/api/v2/application/{applicationId}/attributes
Gets the custom attributes for an application.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>