Install Jentic One Beta

Connect the Sifter API to your agent

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

List all projects

Get project details

Create an issue

Query and filter Sifter API records by parameters

Monitor Sifter API operational status and events

Use Cases

GET STARTED

Start building with Sifter API

Explore with Jentic One

View OpenAPI Document

Automated Projects Management

Automate projects operations by combining multiple Sifter API endpoints. Agents can get project details and then get project milestones in a single workflow.

Call GET /projects/{projectId} to get project details, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Sifter 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 'list all projects', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

11 endpoints — sifter is a simple hosted bug and issue tracker.

METHOD

PATH

DESCRIPTION

GET

/projects

List all projects

GET

/projects/{projectId}

Get project details

GET

/projects/{projectId}/milestones

Get project milestones

GET

/projects/{projectId}/categories

Get project categories

GET

/projects/{projectId}/people

Get project people

POST

/projects/{projectId}/issues

Create an issue

GET

/projects/{projectId}/issues

List project issues

POST

/projects/{projectId}/issues/{issueId}

Create a comment on an issue

GET

/projects

List all projects

GET

/projects/{projectId}

Get project details

GET

/projects/{projectId}/milestones

Get project milestones

GET

/projects/{projectId}/categories

Get project categories

GET

/projects/{projectId}/people

Get project people

POST

/projects/{projectId}/issues

Create an issue

GET

/projects/{projectId}/issues

List project issues

POST

/projects/{projectId}/issues/{issueId}

Create a comment on an issue

Why Jentic?

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

Setup

Wiring Sifter by hand means sending its X-Sifter-Token header, resolving your account subdomain into https://{account}.sifterapp.com/api, and walking project ids yourself. Through Jentic you install once, import Sifter from the API Directory, store the token once, and your agent calls it.

Permission scoping

Sifter puts the project id in the URL path (/projects/{projectId}), so a rule can pin your agent to one project: it can read that project's milestones, people, and issues and nothing else. You choose the operations it may call, so writing new issues is not included unless you add it.

Credential isolation

Your Sifter token 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 'list all projects' or 'create an issue', and Jentic returns the matching Sifter operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Sifter API through Jentic.

What authentication does the Sifter API use?

The Sifter API uses an API key passed in the `X-Sifter-Token` 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 list all projects with the Sifter API?

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

What are the rate limits for the Sifter 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 list all projects through Jentic?

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

How many endpoints does the Sifter API have?

The Sifter API exposes 11 endpoints covering projects, issues, comments operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Sifter operations and credentials the agent may use. Since Sifter carries the project id in the URL path (/projects/{projectId}), a rule can pin the agent to a single project so it only reads that project's milestones, people, and issues. You also choose the operations it may call, so writing new issues via POST /projects/{projectId}/issues stays off unless you grant it.

Sifterapp Sifter API

Name: Sifter API
Brand: Sifter API
Availability: InStock

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsProject ManagementapiKey11 EndpointsREST

For Agents

Programmatically list all projects, get project details. Covers 11 operations with apiKey authentication.

Use for: I need to all projects, I want to project details, Search for project milestones, Find all project categories

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

Sifter is a simple hosted bug and issue tracker. The API provides read and limited write access to projects, issues, comments, statuses, and priorities. The API exposes 11 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

44%

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.

55%

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

76%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Sifter API to your agent

Capabilities

Use Cases

Start building with Sifter API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Sifterapp Sifter API

Jentic AI Readiness Score

Sifter 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