Install Jentic One Beta

Connect the Supabugs Public API to your agent

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

Create Issue

Issues Index for Zapier

Search Issues

Get Issue

Update Issue

GET STARTED

Start building with Supabugs Public API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Supabugs Public API for, with concrete tasks.

★ Analytics Operations

Use the Supabugs Public API to perform analytics operations programmatically. The API provides 13 endpoints covering core functionality including create issue, issues index for zapier, search issues.

Call POST /issues to create issue

Automated Attachments Management

Automate attachments operations by combining multiple Supabugs Public API endpoints. Agents can issues index for zapier and then search issues in a single workflow.

Call GET /issues to issues index for zapier, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Supabugs Public 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 apiKey tokens manually.

Search Jentic for 'create issue', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

13 endpoints — supabugs public api for managing issues, comments, attachments, and projects in bug tracking workflows.

METHOD

PATH

DESCRIPTION

POST

/issues

Create Issue

GET

/issues

Issues Index for Zapier

POST

/issues/search

Search Issues

GET

/issues/{id}

Get Issue

PUT

/issues/{id}

Update Issue

DELETE

/issues/{id}

Delete Issue

POST

/issues/{id}/comments

Add Comment to Issue

DELETE

/issues/{issueId}/comments/{id}

Delete Comment

POST

/issues

Create Issue

GET

/issues

Issues Index for Zapier

POST

/issues/search

Search Issues

GET

/issues/{id}

Get Issue

PUT

/issues/{id}

Update Issue

DELETE

/issues/{id}

Delete Issue

POST

/issues/{id}/comments

Add Comment to Issue

DELETE

/issues/{issueId}/comments/{id}

Delete Comment

Why Jentic?

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

Setup

Wiring the Supabugs Public API by hand means passing its API key as an Authorization header bearer token and handling retries yourself. Through Jentic you install once, import the Supabugs Public API from the API Directory, store the key once, and your agent calls it.

Permission scoping

The Supabugs Public API puts the issue id in the URL path (/issues/{id}), so a rule can pin your agent to one issue: it can read the issue and its comments and nothing else. You choose the operations it may call, so destructive ones like deleting an issue or a comment are not included unless you add them.

Credential isolation

Your Supabugs Public API key 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 'create an issue' or 'search issues', and Jentic returns the matching Supabugs Public API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Supabugs Public API through Jentic.

What authentication does the Supabugs Public API use?

The Supabugs Public API uses an API key passed in the `Authorization` header. 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 create issue with the Supabugs Public API?

Yes. Use the POST /issues endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Supabugs Public 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 create issue through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create issue'. Jentic returns the matching Supabugs Public API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Supabugs Public API have?

The Supabugs Public API exposes 13 endpoints covering attachments, comments, issues operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Supabugs Public API operations and credentials the agent may use. Since the issue id sits in the URL path (/issues/{id}), you can pin the agent to a single issue so it only reads that issue and its comments, and you pick exactly which operations it may call. Destructive calls like deleting an issue (DELETE /issues/{id}) or removing a comment stay off unless you add them.

Supabugs Public API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyAnalyticsWeb AnalyticsapiKey13 EndpointsREST

For Agents

Programmatically create issue, issues index for zapier. Covers 13 operations with apiKey authentication.

Use for: I need to issue, I want to issues index for zapier, Search for issues, Find all issue

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

Supabugs public API for managing issues, comments, attachments, and projects in bug tracking workflows. The API exposes 13 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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

100%

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.

50%

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

32%

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.

57%

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.

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Supabugs Public API to your agent

Capabilities

Start building with Supabugs Public API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Supabugs Public API

Jentic AI Readiness Score

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