Install Jentic One Beta

Connect the Repology API to your agent

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

Get packages for a single project

List projects

Integrate Repology API into automated workflows

Query and filter Repology API records by parameters

Monitor Repology API operational status and events

GET STARTED

Start building with Repology API

Explore with Jentic One

View OpenAPI Document

Automated Maintainer Management

Automate maintainer operations by combining multiple Repology API endpoints. Agents can list projects and then list projects starting from a name in a single workflow.

Call GET /api/v1/projects/ to list projects, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Repology 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 'get packages for a single project', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

6 endpoints — repology api provides access to package and project data across software repositories.

METHOD

PATH

DESCRIPTION

GET

/api/v1/project/{projectName}

Get packages for a single project

GET

/api/v1/projects/

List projects

GET

/api/v1/projects/{startName}/

List projects starting from a name

GET

/api/v1/projects/..{endName}/

List projects ending at a name

GET

/api/v1/repository/{repoName}/problems

Get problems for a repository

GET

/api/v1/maintainer/{maintainer}/problems-for-repo/{repoName}

Get maintainer problems for a repository

GET

/api/v1/project/{projectName}

Get packages for a single project

GET

/api/v1/projects/

List projects

GET

/api/v1/projects/{startName}/

List projects starting from a name

GET

/api/v1/projects/..{endName}/

List projects ending at a name

GET

/api/v1/repository/{repoName}/problems

Get problems for a repository

GET

/api/v1/maintainer/{maintainer}/problems-for-repo/{repoName}

Get maintainer problems for a repository

Why Jentic?

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

Setup

Wiring Repology by hand means constructing its project and repository paths against the repology.org host and handling the range-based project paging yourself. Through Jentic you install once, import the Repology API from the API Directory, and your agent calls it.

Permission scoping

Repology puts the project name in the URL path (/api/v1/project/{projectName}), so a rule can pin your agent to reading one project's packages. Every operation is read-only, and you choose which of them the agent may call.

Credential isolation

Any credential this read-only API needs 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 'get packages for a single project' or 'list repository problems', and Jentic returns the matching Repology operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Repology API through Jentic.

What authentication does the Repology API use?

The Repology 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 get packages for a single project with the Repology API?

Yes. Use the GET /api/v1/project/{projectName} endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Repology 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 get packages for a single project through Jentic?

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

How many endpoints does the Repology API have?

The Repology API exposes 6 endpoints covering maintainer, project, projects operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Repology operations and credentials the agent may use. Since the project name sits in the URL path (GET /api/v1/project/{projectName}), you can pin the agent to reading a single project's packages, and you choose which of the other read-only calls, such as listing projects or fetching repository problems, it is allowed to make. Every Repology operation is read-only, so the agent can query package and repository data but cannot change anything.

Repology API

Name: Repology API
Brand: Repology API
Availability: InStock

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsPackage Registrynone6 EndpointsREST

For Agents

Programmatically get packages for a single project, list projects. Covers 6 operations.

Use for: I need to packages for a single project, I want to projects, Search for projects starting from a name, Find all projects ending at a name

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

Repology API provides access to package and project data across software repositories. It allows querying projects, packages, and repository problems. The API exposes 6 endpoints.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

75%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

38%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

60%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

71%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Repology API to your agent

Capabilities

Start building with Repology API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Repology API

Jentic AI Readiness Score

Repology API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness