Official vendor OpenAPI document · agent-readyDeveloper 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.
Use for: I need to creates a platform_config within the current organisation, I want to shows the platform_configs, Search for updates an platform_config within the current organisation., Find all marks a platform_config as deleted within the current organisation.
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
This API allows developers to communicate with the REALCUBE platform. Admins can also access the [admin area](https://api.realcube.com). The API exposes 390 endpoints secured 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.
1
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%2Frealcube.com%2Frealcube" | sh2
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%2Frealcube.com%2Frealcube" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
Returns all users within the given account.
Login
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
Login
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.
GET
/v1/users
Returns all users within the given account.
POST
/v1/users/log_in
Login
GET
/v1/users/refresh_token
Refresh token
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
R
REALCUBE API
- Foundational (D)43/100
44
Foundational Compliance74
Developer Experience & Jentic Compatibility25
AI-Readiness & Agent Experience42
Agent Usability70
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
44
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: DSignals: 4
76%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
0%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
74
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
27%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
75%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
93%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
25
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
37%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
64%
Summary Coverage
Coverage of summaries across operations/tags/info.
42
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: D-Signals: 1
42%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
70
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
70%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the REALCUBE API by hand means choosing between its API-key request header and OAuth2 flow, managing login and refresh_token calls, and navigating hundreds of endpoints for platform configs and users yourself. Through Jentic you install once, import the REALCUBE API from the API Directory, store the credential once, and your agent calls it.
Permission scoping
The REALCUBE API puts the resource id in the URL path (/v1/platform_configs/{platform_config_id}), so a rule can pin your agent to one platform config. You choose the operations it may call, so a destructive one like deleting a platform config is not included unless you add it.
Credential isolation
Your REALCUBE API 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 'create a platform config' or 'list users in the organisation', and Jentic returns the matching REALCUBE API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.
Can I limit what my agent is allowed to do with the REALCUBE API?
Yes. Because you self-host Jentic One, your own rules decide which REALCUBE API operations and credentials the agent may use, so you can grant read calls like GET /v1/platform_configs or GET /v1/users while leaving out a destructive one such as DELETE /v1/platform_configs/{platform_config_id}. Since the resource id sits in the URL path, a rule can pin the agent to a single platform config rather than the whole organisation. The stored credential is injected only for the operations you have allowed.
GET STARTED