Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Skhokho 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%2Fskhokho.io%2Fskhokho" | 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%2Fskhokho.io%2Fskhokho" | 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 Skhokho API.
Create Accounts
List Accounts
Integrate Skhokho API into automated workflows
Query and filter Skhokho API records by parameters
Monitor Skhokho API operational status and events
GET STARTED
Patterns agents use Skhokho API for, with concrete tasks.
★ Finance and Accounting Operations
Use the Skhokho API to perform finance operations programmatically. The API provides 24 endpoints covering core functionality including create accounts, list accounts, create clients.
Call POST /accounts to create accounts
Automated Accounts Management
Automate accounts operations by combining multiple Skhokho API endpoints. Agents can list accounts and then create clients in a single workflow.
Call GET /accounts to list accounts, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Skhokho 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 basic tokens manually.
Search Jentic for 'create accounts', load the operation schema, and execute with Jentic-managed credentials
24 endpoints — skhokho business management api for accounting, projects, and crm.
METHOD
PATH
DESCRIPTION
/accounts
Create Accounts
/accounts
List Accounts
/clients
Create Clients
/clients
List Clients
/products
Create Products
/products
List Products
/quotes
Create Quotes
/quotes
List Quotes
/accounts
Create Accounts
/accounts
List Accounts
/clients
Create Clients
/clients
List Clients
/products
Create Products
/products
List Products
/quotes
Create Quotes
/quotes
List Quotes
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Skhokho API by hand means setting up HTTP basic auth and carrying those credentials across every account, client, product, and quote call yourself. Through Jentic you install once, import Skhokho from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Skhokho carries its targets in the request body rather than as a resource id in the URL path, so scope the agent by operations: limit it to the operations it needs, such as listing clients or products, and leave out creating accounts or quotes unless you add them.
Credential isolation
Your Skhokho basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'list clients' or 'create a quote', and Jentic returns the matching Skhokho 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 Skhokho API through Jentic.
What authentication does the Skhokho API use?
The Skhokho API uses HTTP Basic authentication with username and password. 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 create accounts with the Skhokho API?
Yes. Use the POST /accounts endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Skhokho 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 create accounts through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create accounts'. Jentic returns the matching Skhokho API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Skhokho API have?
The Skhokho API exposes 24 endpoints covering accounts, clients, contacts operations.
Can I limit what my agent is allowed to do with the Skhokho API?
Yes. Because you run Jentic One yourself and set its rules, you decide which Skhokho operations your agent may call and which stored credentials it may use. Skhokho passes its targets in the request body rather than as an id in the URL path, so you scope the agent by operation: allow only what it needs, such as listing clients (GET /clients) or listing products (GET /products), and leave out create operations like POST /accounts or POST /quotes unless you grant them. The agent can call nothing you have not explicitly allowed.
For Agents
Programmatically create accounts, list accounts. Covers 24 operations with basic authentication.
Use for: I need to accounts, I want to accounts, Search for clients, Find all clients
Not supported: Does not handle payments, communications, or crm - use for finance and accounting only.
Skhokho business management API for accounting, projects, and CRM. The API exposes 24 endpoints secured with basic 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>