Install Jentic One Beta

Connect the Krova Cloud API to your agent

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

Provision a Cube from an OS image with vcpu, ramGb, and diskGb resources, an sshPublicKey, an optional region, and a cloud-init userData script

Power off, wake, or restart a Cube, and toggle terminationProtection so it cannot be deleted by mistake

Attach a custom domain to a Cube with proxy options such as ipAllowList, corsConfig, and responseCompression, then read the DNS records it needs and their live status

Forward TCP ports to a Cube with an optional IP whitelist and UDP support

GET STARTED

Start building with Krova Cloud API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Krova Cloud API for, with concrete tasks.

★ On-Demand Dev and Test Servers

A developer agent spins up a throwaway server for a branch or experiment. It reads available regions and OS images, creates a Cube with the required name, image, resources, and sshPublicKey, fetches SSH connection details for the new Cube, and powers it off or deletes it when the work is done. An Idempotency-Key header on the create call makes a retried request safe.

Call GET /regions and GET /images, then POST /spaces/{spaceId}/cubes with name 'feature-auth-test', image from the list, resources {vcpu: 2, ramGb: 4, diskGb: 40}, and an ssh-ed25519 sshPublicKey, then GET /spaces/{spaceId}/cubes/{cubeId}/ssh

Publishing an App on a Custom Domain

Once an app runs on a Cube, the agent attaches a custom domain and port, reads the DNS records the mapping requires along with their live status, and tunes proxy settings such as securityHeadersMode or ipAllowList through the domain update operation. Raw TCP services such as databases or game servers get a TCP port forward instead.

Call POST /spaces/{spaceId}/cubes/{cubeId}/domains with domain 'app.example.com' and port 3000, then GET /spaces/{spaceId}/cubes/{cubeId}/domains/{mappingId}/records to list the DNS records to create

Snapshot Before Risky Changes

Before an upgrade or migration, the agent snapshots the Cube, performs the change, and restores from the snapshotId if something breaks. Backups can be listed newest first, downloaded through a presigned URL, or offered to another Space, which accepts or declines the share.

Call POST /spaces/{spaceId}/cubes/{cubeId}/snapshots with name 'pre-upgrade', run the upgrade, and on failure call POST /spaces/{spaceId}/cubes/{cubeId}/restore with that snapshotId

AI Agent Infrastructure Control via Jentic

An operations agent drives Krova Cloud through Jentic without handling the X-API-KEY itself. It searches by intent, receives the matching Cube operation with its input schema, and executes with the key injected at run time, so restarting a stuck server or reading webhook deliveries becomes one step in a larger runbook.

Search Jentic for 'restart a Krova Cube', load the POST /spaces/{spaceId}/cubes/{cubeId}/restart schema, and execute it for the target spaceId and cubeId

Key Endpoints

45 endpoints — the krova cloud api provisions and runs cubes, krova's virtual servers, inside a space: create one from an os image with a vcpu, ramgb, and diskgb sizing and an ssh public key, then power it off, wake it, restart it, or delete it.

METHOD

PATH

DESCRIPTION

POST

/spaces/{spaceId}/cubes

Create a Cube

GET

/spaces/{spaceId}/cubes

List Cubes in a Space

POST

/spaces/{spaceId}/cubes/{cubeId}/restart

Restart a running Cube

POST

/spaces/{spaceId}/cubes/{cubeId}/power-off

Power off a running Cube

POST

/spaces/{spaceId}/cubes/{cubeId}/domains

Attach a custom domain

POST

/spaces/{spaceId}/cubes/{cubeId}/snapshots

Create a snapshot

POST

/spaces/{spaceId}/webhooks

Create a webhook endpoint

GET

/regions

List regions with available capacity

POST

/spaces/{spaceId}/cubes

Create a Cube

GET

/spaces/{spaceId}/cubes

List Cubes in a Space

POST

/spaces/{spaceId}/cubes/{cubeId}/restart

Restart a running Cube

POST

/spaces/{spaceId}/cubes/{cubeId}/power-off

Power off a running Cube

POST

/spaces/{spaceId}/cubes/{cubeId}/domains

Attach a custom domain

POST

/spaces/{spaceId}/cubes/{cubeId}/snapshots

Create a snapshot

POST

/spaces/{spaceId}/webhooks

Create a webhook endpoint

GET

/regions

List regions with available capacity

Why Jentic?

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

Setup

Wiring Krova Cloud by hand means sending a Space-scoped X-API-KEY, sending an Idempotency-Key on creates, and staying inside the mutating-call rate limit yourself. Through Jentic you install once, import Krova Cloud from the API Directory, store the key once, and your agent calls it.

Permission scoping

Krova Cloud puts both the Space id and the Cube id in the URL path (/spaces/{spaceId}/cubes/{cubeId}/...), so a rule can pin your agent to one Cube and the operations you pick. You choose that set, so destructive ones like Cube deletion or snapshot deletion are not included unless you add them.

Credential isolation

Your Krova Cloud key 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 'create a virtual server' or 'snapshot a Cube', and Jentic returns the matching Krova Cloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Krova Cloud API through Jentic.

What authentication does the Krova Cloud API use?

Per its OpenAPI spec, the Krova Cloud API uses the ApiKeyAuth scheme: an API key in the X-API-KEY header. Keys are scoped to one Space and inherit the permissions of the membership that created them. The regions, images, and pricing endpoints and the CLI device-login endpoints need no key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at execution time.

What are the rate limits for the Krova Cloud API?

The OpenAPI spec states that mutating POST and DELETE endpoints are rate-limited to 10 requests per 60 seconds per client IP. Reads are not given a limit in the spec, so pace bulk create or delete loops accordingly.

Can I attach a custom domain to a Cube with the Krova Cloud API?

Yes. Send domain and port to the Cube's domains endpoint, with optional proxy settings such as securityHeadersMode, ipAllowList, ipDenyList, corsConfig, and responseCompression. The records endpoint for that mapping then lists the DNS records the domain needs and whether each is live, and the mapping can be updated or detached later.

How do I restart a Cube through Jentic with the Krova Cloud API?

Search Jentic for 'restart a Krova Cube' and it returns the restart operation with its input schema. Execute POST /spaces/{spaceId}/cubes/{cubeId}/restart with the Space and Cube ids, and the key is injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Is there a Krova Cloud MCP server?

You don't need an MCP server to give your agent the Krova Cloud API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered by intent on demand, so no extra server's tool definitions fill the agent's context.

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

Yes. Write a rule that allows only the power-off, wake, and restart operations plus GET on one cubeId, and the agent can recover that single server while every other Cube, snapshot, and domain stays untouched. Each call runs through your own instance, where it is logged.

Krova Cloud API

AI ReadinessFoundational (D)44/100

See full scorecard

Official vendor OpenAPI document · agent-readyCloud InfrastructureComputeapiKey45 EndpointsREST

For Agents

Create, start, stop, and restart Krova Cubes, attach custom domains and TCP forwards, snapshot and restore them, and subscribe to lifecycle webhooks, all within the Space your API key belongs to.

Use for: Spin up a 2 vCPU Ubuntu Cube with my SSH key, Restart the Cube that stopped responding, List the regions that currently have capacity, Take a snapshot of my web server before I upgrade it

Not supported: Does not handle managed databases, Kubernetes clusters, object storage, or domain registration. Use for provisioning and operating Krova Cubes, their domains, snapshots, and backups only.

The Krova Cloud API provisions and runs Cubes, Krova's virtual servers, inside a Space: create one from an OS image with a vcpu, ramGb, and diskGb sizing and an SSH public key, then power it off, wake it, restart it, or delete it. It also attaches custom domains with proxy settings and DNS record checks, forwards TCP ports, takes and restores snapshots, shares backups between Spaces, imports .cube archives, and sends signed webhooks for events such as cube.running or snapshot.created. Keys are scoped per Space and sent in the X-API-KEY header.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B-Signals: 4

74%

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

75%

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.

47%

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

28%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

56%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

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: A-Signals: 1

70%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Krova Cloud API to your agent

Capabilities

Start building with Krova Cloud API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Krova Cloud API

Jentic AI Readiness Score

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