Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the SAIB 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%2Fsaib.com.sa%2Fsaib-com-sa" | 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%2Fsaib.com.sa%2Fsaib-com-sa" | 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 SAIB API.
Get access token
List resources
Integrate SAIB API into automated workflows
Query and filter SAIB API records by parameters
Monitor SAIB API operational status and events
GET STARTED
Patterns agents use SAIB API for, with concrete tasks.
★ Finance and Accounting Operations
Use the SAIB API to perform finance operations programmatically. The API provides 3 endpoints covering core functionality including get access token, list resources, get resource.
Call POST /auth/token to get access token
Automated Authentication Management
Automate authentication operations by combining multiple SAIB API endpoints. Agents can list resources and then get resource in a single workflow.
Call GET /resources to list resources, then verify the result
AI Agent Integration via Jentic
AI agents discover and call SAIB 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 apiKey tokens manually.
Search Jentic for 'get access token', load the operation schema, and execute with Jentic-managed credentials
3 endpoints — saudi investment bank api services.
METHOD
PATH
DESCRIPTION
/auth/token
Get access token
/resources
List resources
/resources/{id}
Get resource
/auth/token
Get access token
/resources
List resources
/resources/{id}
Get resource
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the SAIB API by hand means exchanging its API key for a token at /auth/token, attaching it to each call against api.saib.com.sa, and managing your own retries. Through Jentic you install once, import the SAIB API from the API Directory, store the key once, and your agent calls it.
Permission scoping
SAIB puts the resource id in the URL path (/resources/{id}), so a rule can pin your agent to reading one resource. You choose the operations it may call, so it can list and read resources without any write access unless you add it.
Credential isolation
Your SAIB API key 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 'get an access token' or 'read a resource', and Jentic returns the matching SAIB 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 SAIB API through Jentic.
What authentication does the SAIB API use?
The SAIB API uses an API key passed in the `X-API-Key` 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 get access token with the SAIB API?
Yes. Use the POST /auth/token endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the SAIB 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 get access token through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get access token'. Jentic returns the matching SAIB API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the SAIB API have?
The SAIB API exposes 3 endpoints covering authentication, resources operations.
Can I limit what my agent is allowed to do with the SAIB API?
Yes. Because Jentic One is self-hosted, your own rules decide which SAIB operations and credentials the agent may use. You can allow only the read calls, GET /resources to list resources and GET /resources/{id} to fetch one, while withholding any write access. Since SAIB puts the resource id in the URL path, a rule can even pin the agent to a single resource id.
For Agents
Programmatically get access token, list resources. Covers 3 operations with apiKey authentication.
Use for: I need to access token, I want to resources, Search for resource, List all records from SAIB API
Not supported: Does not handle payments, communications, or crm - use for finance and accounting only.
Saudi Investment Bank API services. The API exposes 3 endpoints secured with apiKey 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>