canonical: https://jentic.com/apis/repology.org/repology

# Repology API

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.

## For AI agents

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

## Scope

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

## Capabilities

- 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

## Use cases

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

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

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

Example prompt: Search Jentic for 'get packages for a single project', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Maintainer** — Operations for maintainer
- **Project** — Operations for project
- **Projects** — Operations for projects
- **Repository** — Operations for repository

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 67 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 53 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 71 / 100
- **View full report:** https://jentic.com/apis/repology.org/repology/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

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

## Related APIs

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

## FAQ

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