Install Jentic One Beta

Connect the Release.com Platform API to your agent

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

Start a build for an app and read its build log

Rebuild or cancel an in-flight build by build id

Spin up an ephemeral environment (space) for an app and tear it down when done

Pause, resume, or extend the expiration of an environment to control cost

Run a deploy pipeline into a space and abort it if it goes wrong

GET STARTED

Start building with Release.com Platform API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Release.com Platform API for, with concrete tasks.

★ Agent-managed preview environments

A coding agent opens a pull request and needs somewhere to test it. Through the Release.com Platform API it creates a space for the app, waits for the deploy pipeline in that space, and reads the instances to find what is running, then deletes the space when the review is done.

Call POST /apps/{app_id}/spaces for the app, then GET /apps/{app_id}/spaces/{space_id}/pipelines to watch the deploy, and DELETE /apps/{app_id}/spaces/{id} once the review closes

Diagnose a failed build

When a build fails, the agent lists the app's builds filtered by branch, opens the failing one, and reads its log to find the error. After a fix lands it can trigger a rebuild of the same build instead of starting from scratch.

Call GET /apps/{app_id}/builds with branch set to the feature branch, then GET /apps/{app_id}/builds/{id}/log for the failed build, and POST /apps/{app_id}/builds/{id}/rebuild after the fix

Control environment cost

Idle ephemeral environments cost money. An agent can pause spaces outside working hours and resume them in the morning, extend the expiration of one still under review, or override its schedule for a demo.

Call POST /apps/{app_id}/spaces/{id}/pause for each idle space at night and POST /apps/{app_id}/spaces/{id}/resume the next morning

Cluster access and maintenance

Account-level cluster operations let an agent list an account's clusters, verify one, download its kubeconfig for kubectl access, generate a certificate, list database snapshots, or start an upgrade.

Call GET /accounts/{account_id}/clusters, then GET /accounts/{account_id}/clusters/{id}/kubeconfig for the target cluster

Key Endpoints

79 endpoints — the release.

METHOD

PATH

DESCRIPTION

POST

/apps/{app_id}/spaces

Create an environment for an app

POST

/apps/{app_id}/builds

Create a build

GET

/apps/{app_id}/builds/{id}/log

Read a build log

POST

/apps/{app_id}/spaces/{space_id}/pipelines

Run a deploy pipeline in a space

PUT

/apps/{app_id}/spaces/{space_id}/pipelines/{id}/abort

Abort a deploy

POST

/apps/{app_id}/spaces/{id}/pause

Pause an environment

PUT

/apps/{app_id}/spaces/{id}/extend_expiration

Extend environment expiration

GET

/accounts/{account_id}/clusters/{id}/kubeconfig

Download cluster kubeconfig

POST

/apps/{app_id}/spaces

Create an environment for an app

POST

/apps/{app_id}/builds

Create a build

GET

/apps/{app_id}/builds/{id}/log

Read a build log

POST

/apps/{app_id}/spaces/{space_id}/pipelines

Run a deploy pipeline in a space

PUT

/apps/{app_id}/spaces/{space_id}/pipelines/{id}/abort

Abort a deploy

POST

/apps/{app_id}/spaces/{id}/pause

Pause an environment

PUT

/apps/{app_id}/spaces/{id}/extend_expiration

Extend environment expiration

GET

/accounts/{account_id}/clusters/{id}/kubeconfig

Why Jentic?

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

Setup

Wiring Release.com by hand means sending both the X-User-Email and X-User-Token headers on every call and tracking app, space, and pipeline ids across nested paths. Through Jentic you install once, import Release.com from the API Directory, store both values once, and your agent calls it.

Permission scoping

Release.com puts the app id in the URL path (/apps/{app_id}/...), and the space id under it, so a rule can pin your agent to one app or one environment. You choose the operations it may call, so destructive ones like app deletion or cluster upgrades are not included unless you add them.

Credential isolation

Your Release.com email and token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a preview environment' or 'abort a deploy', and Jentic returns the matching Release.com operation with its input schema so the agent calls the right endpoint.

FAQs

Specific to using Release.com Platform API through Jentic.

What authentication does the Release.com Platform API use?

Per its OpenAPI spec, requests carry two API key headers together: X-User-Email with the user's email address and X-User-Token with the user's token, which the spec notes comes from ~/.release.yaml. Through Jentic, both values are stored encrypted by your own Jentic One instance and injected at execution time.

Can I pause or extend an ephemeral environment with the Release.com API?

Yes. Spaces have pause and resume operations, an extend_expiration operation that pushes back the expiry, and an override_schedule operation, all addressed by app id and space id in the path.

How do I read a build log through Jentic?

Search Jentic for 'get a Release build log'. It returns GET /apps/{app_id}/builds/{id}/log with its input schema; your agent supplies the app id and build id, and Jentic sends the request with your stored headers.

What are the rate limits for the Release.com Platform API?

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

Is there a Release.com MCP server?

You don't need an MCP server to give your agent Release.com. Jentic connects it directly from the API Directory: import it, store your email and token once, and your agent calls it. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I limit what my agent is allowed to do with the Release.com Platform API?

Yes. For example, allow GET and POST under /apps/123/spaces plus the pause and resume operations, and your agent can create and park environments for that one app but cannot delete apps, touch clusters, or work on any other app. Every call it makes is logged.

Release.com Platform API

AI ReadinessFoundational (C+)57/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsCi CdapiKey (X-User-Email + X-User-Token headers)79 EndpointsREST

For Agents

Create builds, spin up and pause ephemeral environments, run and abort deploy pipelines, and manage clusters on Release.com. Every operation sends the X-User-Email and X-User-Token headers.

Use for: Spin up a preview environment for my app on Release, Pause the staging environment overnight, Extend the expiration of an ephemeral environment, Get the build log for the failed Release build

Not supported: Does not handle source control hosting, code review, or application monitoring. Use for Release.com builds, ephemeral environments, deploy pipelines, and clusters only.

The Release.com Platform API runs the ephemeral environments, builds, and deploy pipelines behind Release.com. Apps hold builds you can create, rebuild, cancel, and read logs for, while spaces are the environments that apps deploy into, which you can create, pause, resume, extend before they expire, or delete. Pipelines deploy into a space and can be aborted mid-run, and account-level calls cover clusters with kubeconfig download, certificate generation, upgrades, and database snapshot listing.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

95%

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

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: D+Signals: 4

39%

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.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

89%

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

35%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Release.com Platform API to your agent

Capabilities

Start building with Release.com Platform API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Release.com Platform API

Jentic AI Readiness Score

Release.com Platform 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