canonical: https://jentic.com/apis/zube.io/zube

# Zube API

Project management and issue tracking API for agile teams. The API exposes 22 endpoints secured with bearer authentication.

## For AI agents

Programmatically get access token, get current user. Covers 22 operations with bearer authentication.

## Scope

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

## Capabilities

- Get access token
- List accounts
- Add account member
- Create project
- Monitor Zube API operational status and events

## Use cases

### Analytics Operations

Use the Zube API to perform analytics operations programmatically. The API provides 22 endpoints covering core functionality including get access token, get current user, list accounts.

Example prompt: Call POST `/users/tokens` to get access token

### Automated Accounts Management

Automate accounts operations by combining multiple Zube API endpoints. Agents can get current user and then list accounts in a single workflow.

Example prompt: Call GET /current_person to get current user, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Zube 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 bearer tokens manually.

Example prompt: Search Jentic for 'get access token', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/users/tokens` | Get access token |
| GET | `/current_person` | Get current user |
| GET | `/accounts` | List accounts |
| GET | `/accounts/{account_id}` | Get account |
| POST | `/accounts/{account_id}/members` | Add account member |
| GET | `/accounts/{account_id}/members` | List account members |
| POST | `/projects` | Create project |
| GET | `/projects` | List projects |

## Key resources

- **Accounts** — Operations for accounts
- **Cards** — Operations for cards
- **Current_Person** — Operations for current_person
- **Projects** — Operations for projects
- **Users** — Operations for users

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 99 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 61 / 100
- **View full report:** https://jentic.com/apis/zube.io/zube/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 the Zube API by hand means exchanging your key for a bearer token via `/users/tokens`, sending it on the zube.io/api host, and refreshing it yourself. Through Jentic you install once, import Zube from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Zube puts the account id in the URL path (`/accounts/{account_id}/members`), so a rule can pin your agent to one account: it can read that account and list its members and nothing else. You choose the operations it may call, so ones like adding a member or creating a project are not included unless you add them.
- **Credential handling:** Your Zube bearer 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 'get an access token' or 'list account members', and Jentic returns the matching Zube operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Zube API use?

The Zube API uses a Bearer token 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 get access token with the Zube API?

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

### What are the rate limits for the Zube 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 access token through Jentic?

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

### How many endpoints does the Zube API have?

The Zube API exposes 22 endpoints covering accounts, cards, current_person operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Zube operations and credentials the agent may use. Because Zube puts the account id in the URL path, such as `/accounts/{account_id}/members`, you can pin the agent to a single account and let it only read that account and list its members. Write operations like adding a member with POST `/accounts/{account_id}/members` or creating a project with POST /projects stay out of reach unless you explicitly allow them.