Install Jentic One Beta

Connect the Qubole Data Service API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Qubole Data Service 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%2Fqubole.com%2Fqubole" | 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%2Fqubole.com%2Fqubole" | 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 Qubole Data Service API.

Create a new cluster

Get configuration details of all clusters

View a cluster configuration

Edit a cluster configuration

Delete a cluster

GET STARTED

Start building with Qubole Data Service API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Qubole Data Service API for, with concrete tasks.

★ Cloud Infrastructure Operations

Use the Qubole Data Service API to perform cloud infrastructure operations programmatically. The API provides 10 endpoints covering core functionality including create a new cluster, get configuration details of all clusters, view a cluster configuration.

Call POST /v1.3/clusters to create a new cluster

Automated V1.2 Management

Automate v1.2 operations by combining multiple Qubole Data Service API endpoints. Agents can get configuration details of all clusters and then view a cluster configuration in a single workflow.

Call GET /v1.3/clusters to get configuration details of all clusters, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Qubole Data Service 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 'create a new cluster', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

10 endpoints — rest api for qubole data service.

METHOD

PATH

DESCRIPTION

POST

/v1.3/clusters

Create a new cluster

GET

/v1.3/clusters

Get configuration details of all clusters

GET

/v1.3/clusters/{clusterId}

View a cluster configuration

PUT

/v1.3/clusters/{clusterId}

Edit a cluster configuration

DELETE

/v1.3/clusters/{clusterId}

Delete a cluster

PUT

/v1.3/clusters/{clusterId}/{action}

Start or terminate a cluster

POST

/v1.2/commands

Submit a command (Hive, Presto, Spark, etc.)

GET

/v1.2/commands/{commandId}

View command status

POST

/v1.3/clusters

Create a new cluster

GET

/v1.3/clusters

Get configuration details of all clusters

GET

/v1.3/clusters/{clusterId}

View a cluster configuration

PUT

/v1.3/clusters/{clusterId}

Edit a cluster configuration

DELETE

/v1.3/clusters/{clusterId}

Delete a cluster

PUT

/v1.3/clusters/{clusterId}/{action}

Start or terminate a cluster

POST

/v1.2/commands

Submit a command (Hive, Presto, Spark, etc.)

GET

/v1.2/commands/{commandId}

View command status

Why Jentic?

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

Setup

Wiring the Qubole Data Service API by hand means setting its X-AUTH-TOKEN header on every call to api.qubole.com and handling the cluster and command lifecycle responses yourself. Through Jentic you install once, import the Qubole Data Service API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Qubole puts the cluster id in the URL path (/clusters/{clusterId}), so a rule can pin your agent to one cluster: it can read and start or stop that cluster and nothing else. You choose the operations it may call, so destructive ones like deleting a cluster are not included unless you add them.

Credential isolation

Your Qubole auth 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 'create a cluster' or 'run a command', and Jentic returns the matching Qubole operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Qubole Data Service API through Jentic.

What authentication does the Qubole Data Service API use?

The Qubole Data Service API uses an API key passed in the `X-AUTH-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 create a new cluster with the Qubole Data Service API?

Yes. Use the POST /v1.3/clusters endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Qubole Data Service 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 create a new cluster through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new cluster'. Jentic returns the matching Qubole Data Service API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Qubole Data Service API have?

The Qubole Data Service API exposes 10 endpoints covering v1.2, v1.3 operations.

Can I limit what my agent is allowed to do with the Qubole Data Service API?

Yes. Because you run Jentic One yourself, your own rules decide which Qubole operations and credentials the agent may use. Since Qubole puts the cluster id in the URL path (/v1.3/clusters/{clusterId}), you can pin the agent to a single cluster and grant only the calls you want, such as viewing its configuration or starting and terminating it. Destructive operations like DELETE /v1.3/clusters/{clusterId} or submitting arbitrary commands stay off unless you explicitly add them.

Qubole Data Service API

Name: Qubole Data Service API
Brand: Qubole Data Service API
Availability: InStock

AI ReadinessAI-Aware (B-)61/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputeapiKey10 EndpointsREST

For Agents

Programmatically create a new cluster, get configuration details of all clusters. Covers 10 operations with apiKey authentication.

Use for: I need to a new cluster, I want to configuration details of all clusters, Search for view a cluster configuration, Find all edit a cluster configuration

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

REST API for Qubole Data Service. Manage clusters, submit commands (Hive, Presto, Spark, etc.), and view results. The API exposes 10 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

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

14%

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.

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

27%

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.

59%

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

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Qubole Data Service API to your agent

Capabilities

Start building with Qubole Data Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Qubole Data Service API

Jentic AI Readiness Score

Qubole Data Service 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