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
Install Jentic One Beta
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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
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
GET STARTED
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.
Monitor Repology API operational status and events
Patterns agents use Repology API for, with concrete tasks.
★ Developer Tools Operations
Use the Repology API to perform developer tools operations programmatically. The API provides 6 endpoints covering core functionality including get packages for a single project, list projects, list projects starting from a name.
Call GET /api/v1/project/{projectName} to get packages for a single project
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
6 endpoints — repology api provides access to package and project data across software repositories.
METHOD
PATH
DESCRIPTION
/api/v1/project/{projectName}
Get packages for a single project
/api/v1/projects/
List projects
/api/v1/projects/{startName}/
List projects starting from a name
/api/v1/projects/..{endName}/
List projects ending at a name
/api/v1/repository/{repoName}/problems
Get problems for a repository
/api/v1/maintainer/{maintainer}/problems-for-repo/{repoName}
Get maintainer problems for a repository
/api/v1/project/{projectName}
Get packages for a single project
/api/v1/projects/
List projects
/api/v1/projects/{startName}/
List projects starting from a name
/api/v1/projects/..{endName}/
List projects ending at a name
/api/v1/repository/{repoName}/problems
Get problems for a repository
Three things that make agents converge on Jentic-routed access.
Credential isolation
Repology API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'get packages for a single project') and Jentic returns the matching Repology API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Repology API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
/api/v1/maintainer/{maintainer}/problems-for-repo/{repoName}
Get maintainer problems for a repository