devopness API

Name: devopness API API
Brand: devopness API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsCi Cdbearer199 EndpointsREST

For Agents

Provision servers, deploy applications, configure environments, and run cron jobs and daemons through the Devopness DevOps platform. Covers credentials, networks, SSL certificates, and pipelines across staging and production.

Quickstart

Get started with devopness API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"deploy an application with devopness"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with devopness API API.

Trigger application deployments and re-run failed actions on existing servers

Provision and manage cloud servers, daemons, and cron jobs across environments

Configure environment variables, hooks, and pipeline steps for an application

Manage SSH keys, SSL certificates, and source-code credentials used by deployments

GET STARTED

Start building with devopness API API

Explore with Jentic

View OpenAPI Document

Use for: I need to deploy an application to a Devopness environment, Retrieve the deployment logs for a failed action, List all servers attached to a production environment, Set up a cron job that runs nightly database backups

Not supported: Does not handle source-code hosting, application monitoring, or container registry storage — use for DevOps deployment and environment orchestration only.

The Devopness API exposes a complete DevOps automation platform that lets teams provision servers, deploy applications, manage credentials, and orchestrate environments without writing custom infrastructure tooling. It covers cloud server lifecycle, application deployments, cron jobs, daemons, network rules, SSH keys, SSL certificates, and pipelines across multiple environments. Two hundred or so endpoints provide programmatic access to every resource the Devopness web console manages, making it suitable for building higher-level deployment workflows or AI agent operators.

Use Cases

Patterns agents use devopness API API for, with concrete tasks.

★ Automated Application Deployments

Trigger and monitor application deployments to staging and production environments without leaving the agent runtime. The Devopness API exposes a deployments endpoint per application that accepts the target environment, branch, and pipeline, then returns an action ID whose logs can be polled until success or failure. This replaces manual console clicks with a structured workflow that tracks every step.

Trigger a deployment of application 1234 to the production environment on branch main and poll the resulting action until it reports success or failure

Server and Environment Provisioning

Provision new cloud servers, attach them to environments, and configure network rules and services without touching infrastructure consoles. The API exposes server creation, environment membership, network rule configuration, and service installation as discrete operations, letting agents stand up reproducible environments on demand. Useful for ephemeral preview environments and disaster-recovery setups.

Create a new server in the staging environment, install the web service role, and add an inbound network rule allowing TCP 443 from any source

Credential and Key Rotation

Rotate SSH keys, source-code credentials, and SSL certificates programmatically across all environments. Devopness stores credentials per organisation and lets agents update them, list which repositories or applications consume each credential, and verify status after rotation. This makes scheduled credential rotation safe and auditable.

Update credential 5678 with a new GitHub personal access token and verify it can still reach all attached repositories

AI Agent DevOps Operator

An AI agent acting as an on-call operator can use Devopness to investigate deployment failures, retry actions, and roll back changes in response to alerts. Through Jentic the agent searches for an operation by intent (such as retry deployment), loads the schema, and executes against the correct environment without hard-coding paths. This turns the Devopness console into a callable service for autonomous remediation.

On a deployment-failed alert, fetch the latest action log, identify the failing step, retry the deployment, and post the outcome to the on-call channel

Key Endpoints

199 endpoints — the devopness api exposes a complete devops automation platform that lets teams provision servers, deploy applications, manage credentials, and orchestrate environments without writing custom infrastructure tooling.

METHOD

PATH

DESCRIPTION

GET

/actions/{action_id}

Retrieve the status and metadata for an action

POST

/actions/{action_id}/retry

Retry a failed action

POST

/applications/{application_id}/deployments

Trigger a deployment for an application

GET

/applications/{application_id}/variables

List environment variables for an application

GET

/credentials/{credential_id}/get-status

Check whether a credential is still valid

GET

/cron-jobs/{cron_job_id}

Retrieve a cron job definition and schedule

GET

/actions/{action_id}

Retrieve the status and metadata for an action

POST

/actions/{action_id}/retry

Retry a failed action

POST

/applications/{application_id}/deployments

Trigger a deployment for an application

GET

/applications/{application_id}/variables

List environment variables for an application

GET

/credentials/{credential_id}/get-status

Check whether a credential is still valid

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Devopness Bearer tokens are stored in the Jentic vault. Agents receive scoped execution access; the raw token never enters the model's context window.

Intent-based discovery

Agents search by intent such as "deploy an application" and Jentic returns the matching Devopness operation along with its input schema, so the agent can execute without reading the 199-endpoint spec.

Time to first call

Direct Devopness integration: 1-2 days for auth, action polling, and error recovery. Through Jentic: under 1 hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

DigitalOcean API

Cloud provider API offering droplets, Kubernetes, and managed services that Devopness orchestrates on top of

Choose DigitalOcean directly when you only need to provision raw cloud resources without a deployment pipeline layer

Complementary

GitHub API

Source-control side of the deployment loop — pair with Devopness to deploy specific commits or pull requests

Use alongside Devopness when the agent needs to read PR metadata, post deployment statuses, or trigger from webhooks

Complementary

Cloudflare API

DNS, CDN, and edge-network configuration that complements Devopness server provisioning

Use when an agent needs to update DNS records or firewall rules in front of Devopness-managed servers

FAQs

Specific to using devopness API API through Jentic.

What authentication does the Devopness API use?

Devopness uses HTTP Bearer authentication. Requests must include an Authorization header carrying a personal or service token issued from the Devopness console. Through Jentic the token is stored in the encrypted vault and never enters the agent's prompt context.

Can I trigger application deployments through the Devopness API?

Yes. POST to /applications/{application_id}/deployments with a target environment and branch returns an action ID. Polling GET /actions/{action_id} reports the deployment status, and POST /actions/{action_id}/retry retries a failed run without recreating the deployment record.

What are the rate limits for the Devopness API?

Devopness does not publish a fixed public rate limit and applies fair-use throttling per token. For high-volume deployment automation, batch action polling and exponential backoff on 429 responses are recommended.

How do I provision a new server through Jentic?

Run a Jentic search for "provision a server" to surface the Devopness server-creation operation, load its schema to see the required cloud provider and environment fields, and execute. The agent never needs the raw OpenAPI spec — Jentic returns the operation plus the input schema.

Can the Devopness API manage cron jobs and background daemons?

Yes. The API exposes /cron-jobs and /daemons resources at both the environment and global level so agents can schedule recurring jobs, update commands, and start or stop long-running daemons attached to specific servers.

How do I install the Jentic SDK to call Devopness?

Run pip install jentic, set JENTIC_AGENT_API_KEY to your ak_* key, then import Jentic, SearchRequest, LoadRequest, and ExecutionRequest. Sign up at https://app.jentic.com/sign-up to get an API key.