Install Jentic One Beta

Connect the Indicators API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Indicators 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%2Fswaggerhub.pailkun%2Findicators-api" | 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.pailkun%2Findicators-api" | 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 Indicators API.

all indicators

indicator by id

country by code

attribute by code

Monitor Indicators API operational status and events

Use Cases

GET STARTED

Start building with Indicators API

Explore with Jentic One

View OpenAPI Document

Automated indicator Management

Automate indicator operations by combining multiple Indicators API endpoints. Agents can indicator by id and then all countries in a single workflow.

Call GET /indicator/{id} to indicator by id, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Indicators 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 'all indicators', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

21 endpoints — governance indicators api.

METHOD

PATH

DESCRIPTION

GET

/indicator

all indicators

GET

/indicator/{id}

indicator by id

GET

/country

all countries

GET

/country/{code}

country by code

GET

/attribute

all attributes

GET

/attribute/{code}

attribute by code

GET

/type

all types

GET

/type/{code}

type by code

GET

/indicator

all indicators

GET

/indicator/{id}

indicator by id

GET

/country

all countries

GET

/country/{code}

country by code

GET

/attribute

all attributes

GET

/attribute/{code}

attribute by code

GET

/type

all types

GET

/type/{code}

type by code

Why Jentic?

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

Setup

Wiring the Indicators API by hand means pointing at the right AWS eu-west-1 host, matching each indicator, country, and attribute path yourself, and parsing every read response. Through Jentic you install once, import the Indicators API from the API Directory, and since it takes no credential your agent calls it straight away.

Permission scoping

The Indicators API puts the resource id in the URL path (/indicator/{id}, /country/{code}), so a rule can pin your agent to one indicator or country lookup and nothing else. Every endpoint here is a read, so you choose which GET operations it may call and no write reaches the service.

Credential isolation

The Indicators API needs no credential to call, so there is nothing to store. If you add related services later, any credential 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 'look up an indicator' or 'list countries', and Jentic returns the matching Indicators API 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 Indicators API through Jentic.

What authentication does the Indicators API use?

The Indicators 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 all indicators with the Indicators API?

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

What are the rate limits for the Indicators 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 all indicators through Jentic?

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

How many endpoints does the Indicators API have?

The Indicators API exposes 21 endpoints covering indicator, profile, country operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Indicators API operations and lookups the agent may call. Since this API puts the resource id in the URL path, such as GET /indicator/{id} and GET /country/{code}, you can pin the agent to a single indicator or country lookup and block everything else. Every endpoint here is a read, so you choose exactly which GET operations it may run and no write can reach the service.

Pailkun Indicators API

Name: Indicators API
Brand: Indicators API
Availability: InStock

Browse all Swaggerhub Pailkun APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone21 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically all indicators, indicator by id. Covers 21 operations.

Use for: I need to all indicators, I want to indicator by id, Search for all countries, Find all country by code

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

Governance indicators API. The API exposes 21 endpoints.

Jentic One on Github View OpenAPI Document