Install Jentic One Beta

Connect the cubic API to your agent

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

List the organizations your key can view

List the members of an organization

Read a single member by their GitHub user id

Turn a member's seat on or off

Change a member's role within the organization

GET STARTED

Start building with cubic API

Explore with Jentic One

View OpenAPI Document

Membership and role audit

Reviewing who has access to an organization means reading the current member list and each member's role. The cubic API lists members and reads a single member, so an audit can enumerate the organization and flag anyone whose role is higher than expected. A read-only organization key can run this audit without the ability to change anything.

List the members of an organization and read each member's role to produce an access review

Role changes on offboarding

When someone leaves a team, their seat and role need updating promptly. The cubic API updates a member to turn off their seat or change their role, so an offboarding workflow can revoke a seat as soon as the trigger fires. The update operation is the only write in the API, which keeps the blast radius small.

Turn off the seat for a departing member identified by their GitHub user id in a given organization

Key Endpoints

4 endpoints — the cubic api manages the organizations and members tied to a cubic account.

METHOD

PATH

DESCRIPTION

GET

/api/v1/organizations

List the organizations the key can view

GET

/api/v1/organizations/{org}/members

List the members of an organization

GET

/api/v1/organizations/{org}/members/{githubUserId}

Read a single member

PATCH

/api/v1/organizations/{org}/members/{githubUserId}

Turn a seat on or off, or change a role

GET

/api/v1/organizations

List the organizations the key can view

GET

/api/v1/organizations/{org}/members

List the members of an organization

GET

/api/v1/organizations/{org}/members/{githubUserId}

Read a single member

PATCH

/api/v1/organizations/{org}/members/{githubUserId}

Turn a seat on or off, or change a role

Why Jentic?

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

Setup

Wiring the cubic API by hand means handling its bearer-token auth, the difference between personal (cbk_) and organization (cok_) keys, and the read-only limits on an org key yourself. Through Jentic you install once, import cubic from the API Directory, store the key once, and your agent calls it.

Permission scoping

cubic puts the organization id in the URL path (/api/v1/organizations/{org}/...), so a rule can pin your agent to one organization and the member operations you pick. You choose the operations it may call, so the member update that toggles a seat or changes a role is not included unless you add it.

Credential isolation

Your cubic 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 'list organization members' or 'change a member's role', and Jentic returns the matching cubic operation with its input schema so the agent calls the right endpoint without reading the reference docs.

FAQs

Specific to using cubic API through Jentic.

What authentication does the cubic API use?

The cubic API authenticates with a bearer token: a personal API key prefixed cbk_ or an organization key prefixed cok_, as declared in its OpenAPI spec. An organization key with read access can call only the GET operations. Through Jentic the key is stored once and injected at call time, so it never appears in your agent's prompt or logs.

Can a read-only key still change member seats with the cubic API?

No. An organization key with read access can call only the GET operations, so it can list organizations and members and read a single member, but it cannot turn a seat on or off or change a role. A personal key is needed for the update operation.

What are the rate limits for the cubic API?

The OpenAPI spec does not state numeric rate limits for the cubic API. Check the vendor documentation at https://www.cubic.dev for current limits before running frequent member audits.

How do I manage members through Jentic with the cubic API?

Search Jentic for 'list organization members', which returns the GET /api/v1/organizations/{org}/members operation with its input schema, then call it for a given organization. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Because cubic puts the organization id in the URL path, write a rule that allows only the member read operations under one organization, so the agent can list members and read roles but cannot toggle a seat or change a role, and every call it makes is logged.

cubic API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyIdentity AuthDirectory Servicesbearer4 EndpointsREST

For Agents

List the organizations a key can view, read and list organization members, and update a member by toggling their seat or changing their role.

Use for: List the organizations I can access, List the members of an organization, Get a member's role and seat status, Turn a member's seat off

Not supported: Does not handle code review, repositories, or billing. Use for organization member and seat management only.

The cubic API manages the organizations and members tied to a cubic account. It lists the organizations a key can view, lists and reads the members of an organization, and updates a member by turning their seat on or off or changing their role. A personal key sees everything the key owner can, while a read-only organization key is limited to the read operations.

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.

75%

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: DSignals: 4

33%

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.

50%

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: B-Signals: 1

60%

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: C+Signals: 1

59%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the cubic API to your agent

Capabilities

Start building with cubic API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

cubic API

Jentic AI Readiness Score

cubic 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