Install Jentic One Beta

Connect the Borneo to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Borneo, 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%2Fswaggerhub.ciss9%2Fborneo" | sh

Step 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%2Fswaggerhub.ciss9%2Fborneo" | sh
jentic register       # connects your agent to your Jentic One instance

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

Capabilities

What an agent can do with Borneo API.

Solvency request

Cancel solvency request

Validation of payment request

Printing request

Scanner reading request

GET STARTED

Start building with Borneo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Borneo API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

9 endpoints — borneo api : interfacing by api between integrated peripherals & http.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Borneo API through Jentic.

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.

Ciss9 Borneo

Name: Borneo API
Brand: Borneo
Availability: InStock

Browse all Swaggerhub Ciss9 APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone9 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to solvency request, I want to cancel solvency request, Search for validation of payment request, Find all printing request

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

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

Jentic One on Github View OpenAPI Document