canonical: https://jentic.com/apis/qubole.com/qubole

# Qubole Data Service API

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.

## For AI agents

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

## Scope

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

## Capabilities

- Create a new cluster
- Get configuration details of all clusters
- View a cluster configuration
- Edit a cluster configuration
- Delete a cluster
- Start or terminate a cluster
- Submit a command (Hive, Presto, Spark, etc.)

## Use cases

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

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'create a new cluster', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

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

## Key resources

- **V1.2** — Operations for v1.2
- **V1.3** — Operations for v1.3

## 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:** 61 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 78 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 61 / 100
- **View full report:** https://jentic.com/apis/qubole.com/qubole/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 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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

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