Install Jentic One Beta

Connect the Pagure API to your agent

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

Create and configure Git projects with public/private visibility and namespace organization

Manage issues with custom fields, tags, milestones, assignees, and status transitions

Create, update, comment on, flag, and merge pull requests across forks and branches

List and manage repository branches, tags, and commits

Configure webhooks for project events like push, pull request, and issue updates

GET STARTED

Start building with Pagure API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Pagure API for, with concrete tasks.

★ Automated Issue Creation from External Systems

Integrate Pagure issue tracking with external monitoring, ticketing, or CI/CD systems by creating issues programmatically. POST /project/{namespace}/{repo}/new_issue accepts title, description, assignee, tags, milestone, and custom fields. This supports workflows like creating Pagure issues from GitHub Actions, incident response systems, or customer support platforms.

POST /{namespace}/{repo}/new_issue with title, issue_content, assignee, tags, milestone, and private flag.

Pull Request Review and Merge Workflow

Automate pull request workflows by querying open PRs, posting review comments, applying flags (CI status, linter results), and merging when criteria are met. GET /project/{namespace}/{repo}/pull-requests lists PRs, POST /project/{namespace}/{repo}/pull-request/{id}/comment adds review feedback, and POST /project/{namespace}/{repo}/pull-request/{id}/merge completes the merge. This supports code review bots and automated merge policies.

GET /{namespace}/{repo}/pull-requests?status=Open, then POST /{namespace}/{repo}/pull-request/{id}/merge when flags and reviews pass.

Repository Release Management

Manage Git tags and releases via the API by listing tags, creating new tags, and querying commits. GET /project/{namespace}/{repo}/git/tags returns all tags, and combined with commit endpoints, enables automated changelog generation, version bumping, and release note publishing. This supports CI/CD pipelines that tag releases based on semantic versioning rules.

GET /{namespace}/{repo}/git/tags to list versions, then use commit endpoints to generate changelog.

Project and User Activity Monitoring

Track project activity, user contributions, and repository statistics by querying users, projects, stars, forks, and watchers. GET /projects lists all projects with filters, GET /user/{username}/activity shows user contributions, and GET /project/{namespace}/{repo}/stargazers lists who starred a project. This supports analytics dashboards, contributor recognition, and community health metrics.

GET /user/{username}/activity?date={YYYY-MM-DD} for contributions, GET /projects?fork=false&short=true for project list.

AI Agent for Forge Operations

Let an AI agent manage Pagure forge tasks like creating issues from user reports, triaging PRs, tagging releases, adding collaborators to projects, and configuring webhooks. Through Jentic, the agent searches by intent (e.g., 'create a pagure issue'), loads the schema, and executes with the API token injected securely.

Use Jentic search 'create pagure issue' to find POST /{namespace}/{repo}/new_issue, load schema, execute with title and issue_content.

Key Endpoints

78 endpoints — pagure is a lightweight git-centered forge providing a rest api for managing git repositories, issues, pull requests, tags, branches, users, groups, and projects.

METHOD

PATH

DESCRIPTION

POST

/{namespace}/{repo}/new_issue

Create a new issue

GET

/{namespace}/{repo}/issues

List issues with filters

GET

/{namespace}/{repo}/pull-requests

List pull requests

POST

/{namespace}/{repo}/pull-request/{id}/merge

Merge a pull request

GET

/projects

List projects with filters

GET

/user/{username}/activity

Get user activity

POST

/{namespace}/{repo}/webhook/add

Add a webhook

POST

/{namespace}/{repo}/new_issue

Create a new issue

GET

/{namespace}/{repo}/issues

List issues with filters

GET

/{namespace}/{repo}/pull-requests

List pull requests

POST

/{namespace}/{repo}/pull-request/{id}/merge

Merge a pull request

GET

/projects

List projects with filters

GET

/user/{username}/activity

Get user activity

POST

/{namespace}/{repo}/webhook/add

Add a webhook

Why Jentic?

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

Setup

Wiring Pagure by hand means handling its API-token auth in the Authorization header against pagure.io/api/0, shaping issue and pull-request requests, and building your own retry and error handling. Through Jentic you install once, import the Pagure API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Pagure puts the namespace and repo in the URL path (/{namespace}/{repo}/new_issue), so a rule can pin your agent to one repository: it can open issues and read that repo and nothing else. You choose the operations it may call, so merging a pull request or adding a webhook is not included unless you add them.

Credential isolation

Your Pagure token is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Pagure issue' or 'merge a pull request', and Jentic returns the matching Pagure operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Pagure API through Jentic.

What authentication does the Pagure API use?

The Pagure API uses API key authentication via the Authorization header with format 'token <your-api-token>'. Tokens are obtained from Pagure user settings. Through Jentic, tokens are stored encrypted and injected at execution time.

Can I manage pull requests programmatically with the Pagure API?

Yes. The API supports listing PRs, creating PRs from branches, commenting, applying flags (CI status), and merging. This enables automated code review and merge workflows.

Does the Pagure API support issue tracking?

Yes. The API provides full CRUD for issues including custom fields, tags, milestones, assignees, status updates, and comments. This supports integration with external ticketing and monitoring systems.

How do I configure webhooks through the Pagure API?

Use POST /{namespace}/{repo}/webhook/add with the target URL and event types (push, pull request, issue). Webhooks enable real-time integration with CI/CD, chat, and notification systems.

Is the Pagure API free?

Pagure is open-source software (GPL-2.0) and the public instance at pagure.io is free to use for open-source projects. Self-hosted Pagure instances can be deployed with the same API surface.

Can I list all projects on a Pagure instance?

Yes. GET /projects returns a list of projects with optional filters for forks, short format, username, namespace, tags, and pattern matching. Pagination is supported via page and per_page parameters.

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

Yes. Jentic One runs on your own infrastructure, and your rules decide which Pagure operations and which stored token the agent may use. Because Pagure puts the namespace and repo in the URL path, such as /{namespace}/{repo}/new_issue, you can pin the agent to a single repository and grant only the calls you want, for example opening issues and reading that repo while leaving out merging a pull request or adding a webhook. The agent can invoke only the operations you approve.

Pagure API

AI ReadinessFoundational (C+)59/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey78 EndpointsREST

For Agents

Manage Pagure Git repositories, issues, pull requests, users, groups, webhooks, and project settings through a lightweight forge API.

Use for: Create a new issue in a Pagure project, List open pull requests for a repository, Merge a pull request after review, Add a user to a project group

Not supported: Does not host Git repositories, run CI/CD pipelines, or provide artifact storage - use for forge management (issues, PRs, users, webhooks) via API only. Git operations happen via Git protocol, not REST API.

Pagure is a lightweight Git-centered forge providing a REST API for managing Git repositories, issues, pull requests, tags, branches, users, groups, and projects. The API covers project creation and configuration, issue tracking with metadata and custom fields, pull request lifecycle (create, comment, merge, flag), release management via Git tags, user and group administration, webhook configuration, and repository settings including branch protection and notifications. Authentication uses API tokens obtained from Pagure user settings.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

35%

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: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

43%

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: DSignals: 4

26%

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.

53%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

89%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

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: D+Signals: 1

50%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Pagure API to your agent

Capabilities

Start building with Pagure API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Pagure API

Jentic AI Readiness Score

Pagure 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