Zube API

Name: Zube API
Brand: Zube API
Availability: InStock

✓ Official Vendor SpecAnalyticsWeb Analyticsbearer22 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Zube API to your agent

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

Get access token

List accounts

Add account member

Create project

GET STARTED

Start building with Zube API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Zube API for, with concrete tasks.

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

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.

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.

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

Key Endpoints

22 endpoints — project management and issue tracking api for agile teams.

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

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

Why Jentic?

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

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Zube API through Jentic.

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.

Zube API

Connect the Zube API to your agent

Capabilities

Start building with Zube API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs