REALCUBE API

Name: REALCUBE API
Brand: REALCUBE API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsSource ControlapiKey, oauth2390 EndpointsREST

For Agents

Programmatically creates a platform_config within the current organisation, shows the platform_configs. Covers 390 operations with apiKey, oauth2 authentication.

Install Jentic One Beta

Connect the REALCUBE API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the REALCUBE 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 REALCUBE API.

Creates a platform_config within the current organisation

Shows the platform_configs

Updates an platform_config within the current organisation.

Marks a platform_config as deleted within the current organisation.

GET STARTED

Start building with REALCUBE API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use REALCUBE API for, with concrete tasks.

★ Developer Tools Operations

Use the REALCUBE API to perform developer tools operations programmatically. The API provides 390 endpoints covering core functionality including creates a platform_config within the current organisation, shows the platform_configs, updates an platform_config within the current organisation..

Call POST /v1/platform_configs to creates a platform_config within the current organisation

Automated scorecard_memberships Management

Automate scorecard_memberships operations by combining multiple REALCUBE API endpoints. Agents can shows the platform_configs and then updates an platform_config within the current organisation. in a single workflow.

Call GET /v1/platform_configs to shows the platform_configs, then verify the result

AI Agent Integration via Jentic

AI agents discover and call REALCUBE 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 apiKey, oauth2 tokens manually.

Search Jentic for 'creates a platform_config within the current organisation', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

390 endpoints — this api allows developers to communicate with the realcube platform.

METHOD

PATH

DESCRIPTION

POST

/v1/platform_configs

Creates a platform_config within the current organisation

GET

/v1/platform_configs

Shows the platform_configs

PUT

/v1/platform_configs/{platform_config_id}

Updates an platform_config within the current organisation.

DELETE

/v1/platform_configs/{platform_config_id}

Marks a platform_config as deleted within the current organisation.

POST

/v1/users

Creates a user.

GET

/v1/users

Returns all users within the given account.

POST

/v1/users/log_in

GET

/v1/users/refresh_token

Refresh token

POST

/v1/platform_configs

Creates a platform_config within the current organisation

GET

/v1/platform_configs

Shows the platform_configs

PUT

/v1/platform_configs/{platform_config_id}

Updates an platform_config within the current organisation.

DELETE

/v1/platform_configs/{platform_config_id}

Marks a platform_config as deleted within the current organisation.

POST

/v1/users

Creates a user.

Why Jentic?

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

Credential isolation

REALCUBE API apiKey, oauth2 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., 'creates a platform_config within the current organisation') and Jentic returns the matching REALCUBE API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

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

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using REALCUBE API through Jentic.

What authentication does the REALCUBE API use?

The REALCUBE API uses apiKey, oauth2 authentication. 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 creates a platform_config within the current organisation with the REALCUBE API?

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

What are the rate limits for the REALCUBE 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 creates a platform_config within the current organisation through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'creates a platform_config within the current organisation'. Jentic returns the matching REALCUBE API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the REALCUBE API have?

The REALCUBE API exposes 390 endpoints covering scorecard_memberships, users, manufacturers operations.