RunCloud API

Name: RunCloud API
Brand: RunCloud API
Availability: InStock

✓ Official Vendor SpecCommunicationsPush Notificationsbasic13 EndpointsREST

For Agents

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

I need to test api authentication, I want to a server, Search for servers, Find all shared servers

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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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

GET STARTED

Start building with RunCloud API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use RunCloud API for, with concrete tasks.

★ Communications Operations

Use the RunCloud API to perform communications operations programmatically. The API provides 13 endpoints covering core functionality including test api authentication, create a server, list servers.

Call GET /ping to test api authentication

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

Why Jentic?

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

Credential isolation

RunCloud API basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'test api authentication') and Jentic returns the matching RunCloud API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct RunCloud API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.

RunCloud API

Connect the RunCloud API to your agent

Capabilities

Start building with RunCloud API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs