canonical: https://jentic.com/apis/swaggerhub.pailkun/indicators-api

# Pailkun Indicators API

Governance indicators API. The API exposes 21 endpoints.

## For AI agents

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

## Scope

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

## Capabilities

- all indicators
- indicator by id
- country by code
- attribute by code
- Monitor Indicators API operational status and events

## Use cases

### Developer Tools Operations

Use the Indicators API to perform developer tools operations programmatically. The API provides 21 endpoints covering core functionality including all indicators, indicator by id, all countries.

Example prompt: Call GET /indicator to all indicators

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

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

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

## Key endpoints

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

## Key resources

- **indicator** — Governance indicator values
- **profile** — Country profile indicator (WIP)
- **country** — Country info
- **attribute** — Attribute/indicator info
- **type** — Attribute type info

## Why Jentic

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

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

## FAQ

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