Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SailPoint IdentityNow V3 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%2Fsailpoint.com%2Fsailpoint" | 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%2Fsailpoint.com%2Fsailpoint" | 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 SailPoint IdentityNow V3 API.
List identities
Get identity
Create source
Query and filter SailPoint IdentityNow V3 API records by parameters
Monitor SailPoint IdentityNow V3 API operational status and events
GET STARTED
Patterns agents use SailPoint IdentityNow V3 API for, with concrete tasks.
★ Identity and Authentication Operations
Use the SailPoint IdentityNow V3 API to perform identity auth operations programmatically. The API provides 18 endpoints covering core functionality including list identities, get identity, list accounts.
Call GET /v3/identities to list identities
Automated Access Profiles Management
Automate access profiles operations by combining multiple SailPoint IdentityNow V3 API endpoints. Agents can get identity and then list accounts in a single workflow.
Call GET /v3/identities/{id} to get identity, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SailPoint IdentityNow V3 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 oauth2 tokens manually.
Search Jentic for 'list identities', load the operation schema, and execute with Jentic-managed credentials
18 endpoints — sailpoint identitynow v3 api for identity governance, access management, certifications, and provisioning.
METHOD
PATH
DESCRIPTION
/v3/identities
List identities
/v3/identities/{id}
Get identity
/v3/accounts
List accounts
/v3/accounts/{id}
Get account
/v3/sources
Create source
/v3/sources
List sources
/v3/sources/{id}
Get source
/v3/sources/{id}
Update source
/v3/identities
List identities
/v3/identities/{id}
Get identity
/v3/accounts
List accounts
/v3/accounts/{id}
Get account
/v3/sources
Create source
/v3/sources
List sources
/v3/sources/{id}
Get source
/v3/sources/{id}
Update source
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SailPoint IdentityNow V3 API by hand means running its OAuth2 flow, pointing at your tenant.api.identitynow.com host, and managing your own token refresh and retries. Through Jentic you install once, import the SailPoint IdentityNow V3 API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
SailPoint puts the source id in the URL path (/v3/sources/{id}), so a rule can pin your agent to one source: it can read and update that source and nothing else. You choose the operations it may call, so you can allow read-only lookups of identities and accounts without granting source creation or updates unless you add them.
Credential isolation
Your SailPoint IdentityNow V3 API credential 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 identities' or 'look up an account', and Jentic returns the matching SailPoint IdentityNow V3 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 SailPoint IdentityNow V3 API through Jentic.
What authentication does the SailPoint IdentityNow V3 API use?
The SailPoint IdentityNow V3 API uses OAuth 2.0 for authorization. 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 list identities with the SailPoint IdentityNow V3 API?
Yes. Use the GET /v3/identities endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SailPoint IdentityNow V3 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 list identities through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list identities'. Jentic returns the matching SailPoint IdentityNow V3 API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SailPoint IdentityNow V3 API have?
The SailPoint IdentityNow V3 API exposes 18 endpoints covering access profiles, accounts, certifications operations.
Can I limit what my agent is allowed to do with the SailPoint IdentityNow V3 API?
Yes. Jentic One is self-hosted, so you run it and your own rules decide which SailPoint operations and credentials the agent may use. Because SailPoint puts the source id in the URL path (/v3/sources/{id}), you can pin the agent to a single source and let it read and update only that one. You can also allow read-only lookups such as GET /v3/identities and GET /v3/accounts while withholding source creation and updates until you choose to grant them.
For Agents
Programmatically list identities, get identity. Covers 18 operations with oauth2 authentication.
Use for: I need to identities, I want to identity, Search for accounts, Find all account
Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.
SailPoint IdentityNow V3 API for identity governance, access management, certifications, and provisioning. The API exposes 18 endpoints secured with oauth2 authentication.
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.
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>