canonical: https://jentic.com/apis/skhokho.io/skhokho

# Skhokho API

Skhokho business management API for accounting, projects, and CRM. The API exposes 24 endpoints secured with basic authentication.

## For AI agents

Programmatically create accounts, list accounts. Covers 24 operations with basic authentication.

## Scope

Does not handle payments, communications, or crm - use for finance and accounting only.

## Capabilities

- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create accounts', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/accounts` | Create Accounts |
| GET | `/accounts` | List Accounts |
| POST | `/clients` | Create Clients |
| GET | `/clients` | List Clients |
| POST | `/products` | Create Products |
| GET | `/products` | List Products |
| POST | `/quotes` | Create Quotes |
| GET | `/quotes` | List Quotes |

## Key resources

- **Accounts** — Operations related to Accounts
- **Clients** — Operations related to Clients
- **Contacts** — Operations related to Contacts
- **Expenses** — Operations related to Expenses
- **Hustles** — Operations related to Hustles

## AI readiness

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.

- **Score:** 41 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/skhokho.io/skhokho/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Plaid** — Alternative finance API
- **Xero** — Alternative finance API

## FAQ

### 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.