Install Jentic One Beta

Connect the Qovery API to your agent

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

Deploy, stop, restart, redeploy, or cancel the deployment of a whole environment

Deploy one application at a specific git_commit_id and read its status and deployment history

Clone an environment under a new name, optionally onto another cluster_id or project_id, for previews

Add, override, alias, or import environment variables and secrets for an application

GET STARTED

Start building with Qovery API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Qovery API for, with concrete tasks.

★ Agent-driven deploys through Jentic

A coding agent finishes a change and ships it: through Jentic it calls the Qovery deploy operation for one application with the new git_commit_id, then polls application status and reads the deployment logs. The developer's own Jentic One instance injects the Qovery token, and rules keep the agent to deploy and read operations on that application.

POST /application/{applicationId}/deploy with git_commit_id 'a1b2c3d', then poll GET /application/{applicationId}/status until the deployment finishes

Preview environments per branch

Teams review features in throwaway copies of staging. POST /environment/{environmentId}/clone requires a name and accepts cluster_id, project_id, and mode, after which the clone is deployed and can be stopped with POST /environment/{environmentId}/stop when the review ends.

POST /environment/{environmentId}/clone with name 'preview-feature-login', then POST /environment/{environmentId}/deploy using the id of the new clone

Configuration and secrets management

Applications need configuration at the right scope. Qovery keeps environment variables and secrets at project, environment, and application level, and an application variable can be overridden or aliased, so an agent can roll out a new setting without editing every service.

POST /application/{applicationId}/secret with key 'STRIPE_KEY' and its value, then POST /application/{applicationId}/redeploy

Deployment health monitoring

Ops checks start with status. GET /environment/{environmentId}/statuses returns the environment and service statuses, and GET /environment/{environmentId}/logs returns the deployment logs, which an agent can summarise when a deploy fails.

GET /environment/{environmentId}/statuses, and if any service has failed, GET /environment/{environmentId}/logs and summarise the error

Key Endpoints

564 endpoints — the qovery api deploys and runs applications, containers, databases, and jobs on kubernetes clusters in your own cloud account, organised into organizations, projects, and environments.

METHOD

PATH

DESCRIPTION

POST

/environment/{environmentId}/deploy

Deploy an environment

POST

/application/{applicationId}/deploy

Deploy an application

GET

/application/{applicationId}/status

Get application status

POST

/environment/{environmentId}/clone

Clone an environment

POST

/environment/{environmentId}/stop

Stop an environment

GET

/environment/{environmentId}/logs

List environment deployment logs

POST

/application/{applicationId}/secret

Add a secret to an application

GET

/organization/{organizationId}/cluster

List clusters

POST

/environment/{environmentId}/deploy

Deploy an environment

POST

/application/{applicationId}/deploy

Deploy an application

GET

/application/{applicationId}/status

Get application status

POST

/environment/{environmentId}/clone

Clone an environment

POST

/environment/{environmentId}/stop

Stop an environment

GET

/environment/{environmentId}/logs

List environment deployment logs

POST

/application/{applicationId}/secret

Add a secret to an application

GET

/organization/{organizationId}/cluster

Why Jentic?

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

Setup

Wiring Qovery by hand means choosing between its expiring JWT and its Token-prefixed API token in the Authorization header, then chaining organization, project, environment, and application ids across calls. Through Jentic you install once, import Qovery from the API Directory, store the token once, and your agent calls it.

Permission scoping

Qovery puts the environment and application ids in the URL path (/environment/{environmentId}/deploy, /application/{applicationId}/deploy), so a rule can pin your agent to one environment, such as staging. You choose the operations it may call, so destructive ones like cluster deletion or application uninstall are not included unless you add them.

Credential isolation

Your Qovery 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 'deploy an environment' or 'clone an environment for a preview', and Jentic returns the matching Qovery operation with its input schema so the agent finds the right call among hundreds without browsing the reference docs.

FAQs

Specific to using Qovery API through Jentic.

What authentication does the Qovery API use?

The Qovery OpenAPI spec declares two schemes. bearerAuth is an HTTP bearer JWT, meant for human OIDC sessions and subject to a TTL. ApiKeyAuth is an API token sent in the Authorization header as 'Token' followed by the value, generated for machine-to-machine use without a TTL. For an agent, the API token is the usual choice; Jentic stores it encrypted in your own Jentic One instance and injects it at execution time.

Can I deploy a specific commit with the Qovery API?

Yes. POST /application/{applicationId}/deploy requires git_commit_id in the body and deploys that commit. To redeploy the current version use POST /application/{applicationId}/redeploy, and to ship every service in an environment use POST /environment/{environmentId}/deploy.

What are the rate limits for the Qovery API?

The OpenAPI spec does not specify rate limits. Check the Qovery documentation at https://hub.qovery.com/docs for current limits.

How do I deploy an environment with the Qovery API through Jentic?

Install Jentic One, import the Qovery API from the Jentic API Directory, and store your Qovery API token. Your agent searches for 'deploy an environment', Jentic returns POST /environment/{environmentId}/deploy with its schema, and the agent calls it with the environment id. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Qovery MCP server?

You don't need an MCP server to give your agent Qovery. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it, discovering operations on demand rather than loading hundreds of tool definitions into its context.

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

Yes. Write a rule that allows POST /environment/{environmentId}/deploy, GET /environment/{environmentId}/statuses, and GET /environment/{environmentId}/logs for your staging environment id only. The agent can then ship and check staging, while production, cluster operations, and secret edits stay outside its reach. Every call it makes is logged.

Can the Qovery API create preview environments?

Yes. POST /environment/{environmentId}/clone copies an environment and requires a name; you can also pass cluster_id, project_id, mode, and apply_deployment_rule. Deploy the clone with POST /environment/{environmentId}/deploy and stop it with POST /environment/{environmentId}/stop when you are done.

Qovery API

AI ReadinessFoundational (C-)53/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureContainer Orchestrationbearer, apiKey564 EndpointsREST

For Agents

Deploy, stop, restart, and clone Qovery environments and applications, read their status and deployment logs, and manage environment variables, secrets, clusters, and custom domains.

Use for: Deploy the staging environment now, I want to deploy commit a1b2c3 of the API application, What is the status of my production environment?, Clone the staging environment for a preview of this branch

Not supported: Does not host source code, run CI test suites, or bill cloud usage. Use for deploying and operating applications, databases, and environments on Qovery-managed clusters only.

The Qovery API deploys and runs applications, containers, databases, and jobs on Kubernetes clusters in your own cloud account, organised into organizations, projects, and environments. It deploys, stops, restarts, redeploys, and clones whole environments, deploys a single application at a chosen git_commit_id, and reports status and deployment logs. It also manages clusters, deployment rules and stages, custom domains, and environment variables and secrets at project, environment, and application level.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 4

91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

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: C-Signals: 4

49%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

97%

OperationId Quality

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

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

62%

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: BSignals: 1

67%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Qovery API to your agent

Capabilities

Start building with Qovery API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Qovery API

Jentic AI Readiness Score

Qovery 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