canonical: https://jentic.com/apis/swaggerhub.ciss9/borneo

# Ciss9 Borneo

Borneo API : interfacing by API between integrated peripherals & http. The API exposes 9 endpoints.

## For AI agents

Programmatically solvency request, cancel solvency request. Covers 9 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Solvency request
- Cancel solvency request
- Validation of payment request
- Printing request
- Scanner reading request
- State of the banking hardware

## Use cases

### Developer Tools Operations

Use the Borneo to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including solvency request, cancel solvency request, validation of payment request.

Example prompt: Call POST `/v1/tpa/solvency` to solvency request

### Automated tpa Management

Automate tpa operations by combining multiple Borneo endpoints. Agents can cancel solvency request and then validation of payment request in a single workflow.

Example prompt: Call DELETE `/v1/tpa/solvency` to cancel solvency request, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Borneo 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.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/tpa/solvency` | Solvency request |
| DELETE | `/v1/tpa/solvency` | Cancel solvency request |
| POST | `/v1/tpa/payment` | Validation of payment request |
| POST | `/v1/printer/print` | Printing request |
| GET | `/v1/scanner/read` | Scanner reading request |
| DELETE | `/v1/scanner/read` | Cancellation of the scan request |
| GET | `/v1/tpa/status` | State of the banking hardware |
| GET | `/v1/printer/status` | Printer status request |

## Key resources

- **tpa** — Routes regarding the payment automat
- **scanneur** — Routes regarding scanner
- **imprimante** — Routes regarding printer
- **paiement** — Routes regarding payment itself
- **impression** — Routes regarding printing

## Why Jentic

- **Setup:** Wiring the Borneo API by hand means mapping its terminal, printer, and scanner endpoints, formatting each solvency, payment, and print call, and handling retries yourself. Through Jentic you install once, import the Borneo API from the API Directory, and your agent calls it without you writing that plumbing.
- **Permission scoping:** The terminal, printer, and scanner operations carry their target in the request rather than a resource id in the URL path, so scope the agent to the operations it needs, such as reading terminal status with GET `/v1/tpa/status` or scanner reads with GET `/v1/scanner/read.` You choose the allowed set, so starting a payment with POST `/v1/tpa/payment` is not included unless you add it.
- **Credential handling:** This spec defines no authentication, so there is no credential to store. If you point it at a host that adds a key later, that key is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'check terminal status' or 'read a scanned code', and Jentic returns the matching Borneo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Borneo use?

The Borneo 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 solvency request with the Borneo?

Yes. Use the POST `/v1/tpa/solvency` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Borneo?

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 solvency request through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'solvency request'. Jentic returns the matching Borneo operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Borneo have?

The Borneo exposes 9 endpoints covering tpa, scanneur, imprimante operations.

### Can I limit what my agent is allowed to do with the Borneo API?

Yes. Because you run Jentic One yourself, your own rules decide which Borneo operations and credentials the agent may use, so you allow only the calls it needs. You can scope it to read-only operations such as checking terminal status with GET `/v1/tpa/status` or reading a scan with GET `/v1/scanner/read.` Higher-impact operations like starting a payment with POST `/v1/tpa/payment` stay out of reach unless you explicitly add them to the allowed set.