canonical: https://jentic.com/apis/sifterapp.com/sifterapp

# Sifterapp Sifter API

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.

## For AI agents

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

## Scope

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

## Capabilities

- 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

### Developer Tools Operations

Use the Sifter API to perform developer tools operations programmatically. The API provides 11 endpoints covering core functionality including list all projects, get project details, get project milestones.

Example prompt: Call GET /projects to list all projects

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

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

Example prompt: Search Jentic for 'list all projects', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **Projects** — Project management operations
- **Issues** — Issue management operations
- **Comments** — Comment operations
- **Statuses** — Status metadata
- **Priorities** — Priority metadata

## 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:** 66 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 50 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 76 / 100
- **View full report:** https://jentic.com/apis/sifterapp.com/sifterapp/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 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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

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

## FAQ

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