Clever-Cloud API

Name: Clever-Cloud API
Brand: Clever-Cloud API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputeoauth2324 EndpointsREST

For Agents

Deploy and operate applications on Clever Cloud - manage application lifecycles, environment variables, log drains, add-ons, and billing across organizations.

Install Jentic One Beta

Connect the Clever-Cloud API to your agent

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

Deploy and redeploy applications and read live deployment status across environments

Stream and chunk-fetch application logs and configure long-lived log drains

Manage environment variables and runtime configuration on a per-application basis

GET STARTED

Start building with Clever-Cloud API

Explore with Jentic One

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Clever-Cloud API, keeping it validated and agent-ready. The Clever-Cloud API is the public management interface for the Clever Cloud platform-as-a-service, exposing operations for application deployment, environment configuration, log streaming, billing, organization membership, and add-on provisioning. It covers more than 320 endpoints spanning compute applications, scalability rules, networking, GitHub integrations, OAuth tokens, and consumer accounts. Agents can use it to deploy and operate hosted services, retrieve logs, manage drains, and orchestrate tenant-level billing without touching the Clever Cloud console.

Use Cases

Patterns agents use Clever-Cloud API for, with concrete tasks.

★ Application Deployment Automation

Automate application deployments on Clever Cloud, including triggering builds, redeploying GitHub-linked apps, and updating environment variables before each release. The API exposes deployment endpoints, environment variable management, and event streams so an external system can run a full deploy pipeline without using the Clever Cloud console. Typical setup takes a few hours of integration work for a single environment.

Redeploy the application with appId 'app_abc123' using the GitHub-linked source and verify the latest deployment event reports a successful state

Centralised Log Aggregation

Forward application logs from Clever Cloud into an external observability stack by configuring log drains and consuming the log socket. The API supports per-application drains, chunked log fetches, and SSE streams so that logs can be persisted in tools like Datadog, Loki, or Elasticsearch. Setup typically takes under a day for a basic drain configuration.

Create a syslog log drain for application 'app_abc123' pointing at the customer's external Loki endpoint and confirm the drain id is returned

Multi-Tenant Billing Operations

Pull billing data, invoices, and payment methods for organizations managed on Clever Cloud to power internal finance dashboards or rebill customers in a multi-tenant setup. The API exposes invoice listings, balances, and payment information per owner. A simple billing sync job can be wired up in a few hours.

Retrieve all invoices for owner 'orga_xyz' in the last 90 days and aggregate the total amount due

Agent-Driven Platform Management via Jentic

Expose Clever Cloud as a tool to AI agents through Jentic so that agents can deploy services, rotate environment variables, and triage failed deployments using natural language. Jentic isolates the OAuth credentials and surfaces only the operations relevant to a given intent. A working agent integration takes well under an hour with the Jentic SDK.

Search Jentic for 'deploy a clever cloud application', load the schema, and execute a redeploy on appId 'app_abc123'

Key Endpoints

324 endpoints — jentic publishes the only available openapi specification for clever-cloud api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/logs/{appId}

Fetch logs for an application

POST

/logs/drains

Create a log drain

GET

/application/{appId}/environment

List environment variables for an application

POST

/github/redeploy

Redeploy an application linked to GitHub

GET

/notifications/emailhooks/{ownerId}

List configured email notification hooks for an owner

GET

/products/instances

List available compute instance flavours

GET

/logs/{appId}

Fetch logs for an application

POST

/logs/drains

Create a log drain

GET

/application/{appId}/environment

List environment variables for an application

POST

/github/redeploy

Redeploy an application linked to GitHub

GET

/notifications/emailhooks/{ownerId}

List configured email notification hooks for an owner

Why Jentic?

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

Setup

Wiring the Clever-Cloud API by hand means completing its OAuth flow and threading owner and application ids through calls to api.clever-cloud.com/v2 across its large platform operation set. Through Jentic you install once, import Clever-Cloud from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Clever-Cloud puts the application id in the URL path (/application/{appId}/environment), so a rule can pin your agent to one application: it can read that app's logs and environment and nothing else. You choose the operations it may call, so triggering a GitHub redeploy is not included unless you add it.

Credential isolation

Your Clever-Cloud credential 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 an application's logs' or 'get environment variables in Clever-Cloud', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Clever-Cloud API through Jentic.

Why is there no official OpenAPI spec for Clever-Cloud API?

Clever Cloud does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Clever-Cloud API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Clever-Cloud API use?

Clever Cloud uses OAuth 1.0a-style signed requests against api.clever-cloud.com/v2, requiring consumer key, consumer secret, OAuth token, and OAuth token secret. When called through Jentic, these credentials are stored in your Jentic One instance and never exposed to the agent context - the agent only receives a scoped execution handle.

Can I redeploy a GitHub-linked application with the Clever-Cloud API?

Yes. The /github/redeploy endpoint triggers a redeploy of an application that has been linked to a GitHub repository, and /events/event-socket plus deployment endpoints let you observe the resulting deployment state.

What are the rate limits for the Clever-Cloud API?

Clever Cloud does not document fixed numeric rate limits in the public spec. In practice, throttling applies to high-frequency log socket connections and deployment triggers - keep deployment polling to a few requests per second per application and prefer the SSE log stream over repeated GETs.

How do I stream application logs through Jentic?

Search Jentic for 'stream clever cloud application logs', load the operation against /logs/{appId}/sse, and execute it with the target appId. Jentic returns the streamed log payload and handles the OAuth signing for you.

Can I manage billing and invoices through this API?

Yes. Owner-scoped endpoints expose invoices, payment methods, and balances, which is enough to drive an internal billing dashboard or reconcile customer charges across multiple organisations.

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

Yes. Because you self-host Jentic One, your own rules decide which Clever Cloud operations and credentials the agent may use. Since the application id sits in the URL path, such as /application/{appId}/environment, you can pin the agent to a single app so it only reads that app's logs and environment variables. You also choose the operations it may call, so a GitHub redeploy through /github/redeploy is off limits unless you explicitly add it.

Clever-Cloud API

Connect the Clever-Cloud API to your agent

Capabilities

Start building with Clever-Cloud API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs