canonical: https://jentic.com/apis/realcube.com/realcube

# REALCUBE API

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.

## For AI agents

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

## Scope

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

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

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

## Key endpoints

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

## Key resources

- **scorecard_memberships** — Operations related to scorecard_memberships
- **users** — Benutzer
- **manufacturers** — Hersteller
- **dashboards** — Operations related to dashboards
- **apps** — Anwendungen

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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