Install Jentic One Beta

Connect the AltoroJ REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AltoroJ REST 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%2Ftestfire.net%2Ftestfire" | 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%2Ftestfire.net%2Ftestfire" | 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 AltoroJ REST API.

getAccount

getTransactions

showLastTenTransactions

addUser

changePassword

GET STARTED

Start building with AltoroJ REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use AltoroJ REST API for, with concrete tasks.

★ Developer Tools Operations

Use the AltoroJ REST API to perform developer tools operations programmatically. The API provides 12 endpoints covering core functionality including getaccount, getaccountbalance, gettransactions.

Call GET /account to getaccount

Automated 1. Login Management

Automate 1. login operations by combining multiple AltoroJ REST API endpoints. Agents can getaccountbalance and then gettransactions in a single workflow.

Call GET /account/{accountNo} to getaccountbalance, then verify the result

AI Agent Integration via Jentic

AI agents discover and call AltoroJ REST 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 none tokens manually.

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

Key Endpoints

12 endpoints — testfire.

METHOD

PATH

DESCRIPTION

GET

/account

getAccount

GET

/account/{accountNo}

getAccountBalance

POST

/account/{accountNo}/transactions

getTransactions

GET

/account/{accountNo}/transactions

showLastTenTransactions

POST

/admin/addUser

addUser

POST

/admin/changePassword

changePassword

POST

/feedback/submit

sendFeedback

GET

/feedback/{feedbackId}

getFeedback

GET

/account

getAccount

GET

/account/{accountNo}

getAccountBalance

POST

/account/{accountNo}/transactions

getTransactions

GET

/account/{accountNo}/transactions

showLastTenTransactions

POST

/admin/addUser

addUser

POST

/admin/changePassword

changePassword

POST

/feedback/submit

sendFeedback

GET

/feedback/{feedbackId}

getFeedback

Why Jentic?

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

Setup

Wiring the AltoroJ REST API by hand means resolving its /api base against your own deployment host and coding each account, transaction, and admin call yourself. Through Jentic you install once, import the AltoroJ REST API from the API Directory, store any required credential once, and your agent calls it.

Permission scoping

AltoroJ puts the account number in the URL path (/account/{accountNo}/transactions), so a rule can pin your agent to one account: it can read that account and its transactions and nothing else. You choose the operations it may call, so admin operations like adding a user or changing a password are not included unless you add them.

Credential isolation

Any credential for the AltoroJ REST API 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 'read an account balance' or 'list account transactions', and Jentic returns the matching AltoroJ REST API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using AltoroJ REST API through Jentic.

What authentication does the AltoroJ REST API use?

The AltoroJ REST API 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 getaccount with the AltoroJ REST API?

Yes. Use the GET /account endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the AltoroJ REST 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 getaccount through Jentic?

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

How many endpoints does the AltoroJ REST API have?

The AltoroJ REST API exposes 12 endpoints covering 1. login, 2. account, 3. transfer operations.

Can I limit what my agent is allowed to do with the AltoroJ REST API?

Yes. Jentic One is self-hosted, so your own rules decide which AltoroJ operations and credentials the agent may use. Because the account number sits in the URL path, such as /account/{accountNo}/transactions, you can pin the agent to a single account so it only reads that account and its transactions. You also choose the exact operations it may call, so admin actions like POST /admin/addUser or POST /admin/changePassword stay off limits unless you explicitly grant them.

Testfire AltoroJ REST API

Name: AltoroJ REST API
Brand: AltoroJ REST API
Availability: InStock

Developer ToolsSource Controlnone12 EndpointsREST

For Agents

Programmatically getaccount, getaccountbalance. Covers 12 operations.

Use for: I need to getaccount, I want to getaccountbalance, Search for gettransactions, Find all showlasttentransactions

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

testfire.net/altoroj version 1.0.2. The API exposes 12 endpoints.

Jentic One on Github View OpenAPI Document

Connect the AltoroJ REST API to your agent

Capabilities

Start building with AltoroJ REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Testfire AltoroJ REST API