Install Jentic One Beta

Connect the RunCloud API to your agent

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

Test API authentication

Create a server

List servers

Get server details

Monitor RunCloud API operational status and events

Use Cases

GET STARTED

Start building with RunCloud API

Explore with Jentic One

View OpenAPI Document

Automated Ping Management

Automate ping operations by combining multiple RunCloud API endpoints. Agents can create a server and then list servers in a single workflow.

Call POST /servers to create a server, then verify the result

AI Agent Integration via Jentic

AI agents discover and call RunCloud API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'test API authentication', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

13 endpoints — runcloud api allows you to manage your servers, web applications, databases, and more programmatically.

METHOD

PATH

DESCRIPTION

GET

/ping

Test API authentication

POST

/servers

Create a server

GET

/servers

List servers

GET

/servers/shared

List shared servers

GET

/servers/{id}

Get server details

GET

/servers/{id}/installationscript

Get server installation script

GET

/servers/{id}/stats

Get server stats

GET

/servers/{id}/hardwareinfo

Get server hardware info

GET

/ping

Test API authentication

POST

/servers

Create a server

GET

/servers

List servers

GET

/servers/shared

List shared servers

GET

/servers/{id}

Get server details

GET

/servers/{id}/installationscript

Get server installation script

GET

/servers/{id}/stats

Get server stats

GET

/servers/{id}/hardwareinfo

Get server hardware info

Why Jentic?

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

Setup

Wiring RunCloud by hand means setting up its basic auth against manage.runcloud.io/api/v2 and building your own request handling across the servers collection. Through Jentic you install once, import RunCloud from the API Directory, store the credential once, and your agent calls it.

Permission scoping

RunCloud puts the server id in the URL path (/servers/{id}), so a rule can pin your agent to one server: it can read that server's details and stats and nothing else. You choose the operations it may call, so creating a server is not included unless you add it.

Credential isolation

Your RunCloud basic auth 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 'list my servers' or 'get a server's installation script', and Jentic returns the matching RunCloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using RunCloud API through Jentic.

What authentication does the RunCloud API use?

The RunCloud API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I test API authentication with the RunCloud API?

Yes. Use the GET /ping endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the RunCloud API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I test API authentication through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'test API authentication'. Jentic returns the matching RunCloud API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the RunCloud API have?

The RunCloud API exposes 13 endpoints covering ping, servers operations.

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

Yes. Because Jentic One is self-hosted, you set the rules that decide which RunCloud operations and credentials your agent may use. Since RunCloud puts the server id in the URL path (/servers/{id}), you can pin an agent to a single server so it only reads that server's details and stats through endpoints like GET /servers/{id} and GET /servers/{id}/stats. You choose the operations it may call, so a write action such as POST /servers to create a server is excluded unless you explicitly allow it.

RunCloud API

Name: RunCloud API
Brand: RunCloud API
Availability: InStock

AI ReadinessNon-Ready (F)38/100

See full scorecard

Official vendor OpenAPI document · agent-readyCommunicationsPush Notificationsbasic13 EndpointsREST

For Agents

Programmatically test API authentication, create a server. Covers 13 operations with basic authentication.

Use for: I need to test API authentication, I want to a server, Search for servers, Find all shared servers

Not supported: Does not handle payments, crm, or developer tools - use for communications only.

RunCloud API allows you to manage your servers, web applications, databases, and more programmatically. The API exposes 13 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

98%

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

100%

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

22%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

92%

OperationId Quality

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

52%

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

10%

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

61%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the RunCloud API to your agent

Capabilities

Use Cases

Start building with RunCloud API

Key Endpoints

Why Jentic?

Related APIs

FAQs

RunCloud API

Jentic AI Readiness Score

RunCloud 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