Install Jentic One Beta

Connect the Turbine Labs API to your agent

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

Returns the user object for the account authorized and making this request.

Delete the specified access token.

Creates a new Access Token and associates it with the authenticated user.

Lists Access Tokens that are configured for the authenticated user.

Allows an arbitrary filter to be specified and applied to the org\'s change log.

GET STARTED

Start building with Turbine Labs API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Turbine Labs API for, with concrete tasks.

★ Cloud Infrastructure Operations

Use the Turbine Labs API to perform cloud infrastructure operations programmatically. The API provides 44 endpoints covering core functionality including returns the user object for the account authorized and making this request., delete the specified access token., creates a new access token and associates it with the authenticated user..

Call GET /admin/user/self to returns the user object for the account authorized and making this request.

Automated Zone Management

Automate zone operations by combining multiple Turbine Labs API endpoints. Agents can delete the specified access token. and then creates a new access token and associates it with the authenticated user. in a single workflow.

Call DELETE /admin/user/self/access_token/{access-token-key} to delete the specified access token., then verify the result

AI Agent Integration via Jentic

AI agents discover and call Turbine Labs 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 'returns the user object for the account authorized and making this request.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

44 endpoints — the turbine labs api provides crud operations for core object types, and is mostly resty.

METHOD

PATH

DESCRIPTION

GET

/admin/user/self

Returns the user object for the account authorized and making this request.

DELETE

/admin/user/self/access_token/{access-token-key}

Delete the specified access token.

POST

/admin/user/self/access_tokens

Creates a new Access Token and associates it with the authenticated user.

GET

/admin/user/self/access_tokens

Lists Access Tokens that are configured for the authenticated user.

GET

/changelog/adhoc

Allows an arbitrary filter to be specified and applied to the org\'s change log.

GET

/changelog/cluster-graph/{clusterKey}

get changes related to the indicated cluster

GET

/changelog/domain-graph/{domainKey}

get changes related to the indicated domain

GET

/changelog/route-graph/{routeKey}

get changes related to the indicated route

GET

/admin/user/self

Returns the user object for the account authorized and making this request.

DELETE

/admin/user/self/access_token/{access-token-key}

Delete the specified access token.

POST

/admin/user/self/access_tokens

Creates a new Access Token and associates it with the authenticated user.

GET

/admin/user/self/access_tokens

Lists Access Tokens that are configured for the authenticated user.

GET

/changelog/adhoc

Allows an arbitrary filter to be specified and applied to the org\'s change log.

GET

/changelog/cluster-graph/{clusterKey}

get changes related to the indicated cluster

GET

/changelog/domain-graph/{domainKey}

get changes related to the indicated domain

Why Jentic?

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

Setup

Wiring Turbine Labs API by hand means setting its Authorization key header, tracking cluster, domain, and route keys across calls, and handling errors and retries yourself. Through Jentic you install once, import Turbine Labs API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

Turbine Labs API puts resource keys in the URL path (/changelog/cluster-graph/{clusterKey}, /changelog/route-graph/{routeKey}), so a rule can pin your agent to one cluster or route: it can read that resource's changelog graph and nothing else. You choose the operations it may call, so deleting an access token is not included unless you add it.

Credential isolation

Your Turbine Labs API 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 'read the current user' or 'get a cluster's changelog graph', and Jentic returns the matching Turbine Labs API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Turbine Labs API through Jentic.

What authentication does the Turbine Labs API use?

The Turbine Labs API uses an API key passed 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 returns the user object for the account authorized and making this request. with the Turbine Labs API?

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

What are the rate limits for the Turbine Labs 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 returns the user object for the account authorized and making this request. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'returns the user object for the account authorized and making this request.'. Jentic returns the matching Turbine Labs API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Turbine Labs API have?

The Turbine Labs API exposes 44 endpoints covering zone, proxy, listener operations.

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

Yes. Jentic One runs on your own infrastructure, so your rules decide which Turbine Labs operations and credentials the agent may use. Because the API puts resource keys in the URL path, such as /changelog/cluster-graph/{clusterKey} and /changelog/route-graph/{routeKey}, you can pin the agent to reading one cluster's or route's changelog graph and nothing else. You choose the operations it may call, so an action like DELETE /admin/user/self/access_token/{access-token-key} is excluded unless you explicitly grant it.

Turbine Labs API

AI ReadinessFoundational (C)54/100

See full scorecard

Cloud InfrastructureComputeapiKey44 EndpointsREST

For Agents

Programmatically returns the user object for the account authorized and making this request., delete the specified access token.. Covers 44 operations with apiKey authentication.

Use for: I need to returns the user object for the account authorized and making this request., I want to the specified access token., Search for creates a new access token and associates it with the authenticated user., Find all lists access tokens that are configured for the authenticated user.

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

The Turbine Labs API provides CRUD operations for core object types, and is mostly RESTy. The easiest way to interact with the API is with [tbnctl](https://docs.turbinelabs.io/advanced/tbnctl.html). If you want to make direct HTTP calls, however, you can obtain an access token using tbnctl, and then pass it in the Authorization header, prefixed by `Token `:. The API exposes 44 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

96%

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

75%

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: BSignals: 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: FSignals: 4

56%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

64%

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

62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Turbine Labs API to your agent

Capabilities

Start building with Turbine Labs API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Turbine Labs API

Jentic AI Readiness Score

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