Cube Planning
Cube (Cube Software) is a financial planning & analysis (FP&A) platform that positions itself as an "agentic finance layer" — giving finance teams clean, decision-ready data everywhere FP&A happens by harmonizing data across their existing tool stack (ERPs, accounting, HRIS, CRM, data warehouses, and spreadsheets like Excel and Google Sheets) and automating planning, budgeting, and forecasting workflows. Cube exposes a public REST API at api.cubesoftware.com with 296 operations across 16 tags — dimensions, formulas, data tables, cube data exports, dashboards, connections, tags, attributes, and company/user administration — secured with OAuth 2.0 authorization-code + PKCE and multi-tenant via an X-Company-ID header. Cube is a Battery Ventures portfolio company. Enriched by the API Evangelist pipeline from Cube's public OpenAPI and developer surface.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Cube Planning the way a machine reads it — 48 machine-readable artifacts across 42 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Cube Planning scores 46.5/100 (developing), with a separate agent-readiness read of 69/100 (agent native). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
How we profile Cube Planning
Each block below is one kind of artifact we hold for Cube Planning. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 42
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Cube Planning Agents API
The Agents API from Cube Planning — 7 operation(s) for agents.
Cube Planning Attributes API
Attributes are additional metadata that can be applied to values in the cube. They show up as additional columns in drilldowns, for instance.
Cube Planning Audit Trail API
The audit trail tracks the changes of values within the cube and helps with governance.
Cube Planning Auth API
The Auth API from Cube Planning — 3 operation(s) for auth.
Cube Planning Authentication API
The Cube API supports user authentication via OAuth2 using the OAuth2 Authorization Code Flow. To authenticate via OAuth2, an application must first be registered.
Cube Planning Canvases API
The Canvases API from Cube Planning — 10 operation(s) for canvases.
Cube Planning ChatMessages API
The ChatMessages API from Cube Planning — 2 operation(s) for chatmessages.
Cube Planning ChatSessions API
The ChatSessions API from Cube Planning — 2 operation(s) for chatsessions.
Cube Planning ChatSettings API
The ChatSettings API from Cube Planning — 1 operation(s) for chatsettings.
Cube Planning Comments API
The Comments API from Cube Planning — 2 operation(s) for comments.
Cube Planning Companies API
A user in Cube belongs to one or more companies. Companies are how various teams of employees manage their data (dimensions, etc) and permissions (users, etc).
Cube Planning Company Groups API
The Company Groups API from Cube Planning — 4 operation(s) for company groups.
Cube Planning compliance API
The compliance API from Cube Planning — 1 operation(s) for compliance.
Cube Planning Connections API
Connections to external source systems allow Cube to automatically import source dimensions and transaction data.
Cube Planning ContentType API
The ContentType API from Cube Planning — 2 operation(s) for contenttype.
Cube Planning cube API
The cube API from Cube Planning — 2 operation(s) for cube.
Cube Planning Cube Data API
The data stored in a cube for a company, organized by their dimensions.
Cube Planning Cube Value Range API
The Cube Value Range API from Cube Planning — 4 operation(s) for cube value range.
Cube Planning Currencies API
The Currencies API from Cube Planning — 13 operation(s) for currencies.
Cube Planning Dashboard API
Access the underlying Dashboards of Cube
Cube Planning Data Table Uploads API
Cube often uses uploads as a way to load in transaction data for a given data table or connection. You can use the API to create new uploads, send files, and track the status of...
Cube Planning Data Tables API
Data Tables are a generic way to organize the source dimensions, mappings, uploads, and imports from an outside source into Cube (e.g. ERP connections, imported flat files, spre...
Cube Planning Dimensions API
Dimensions store the organizational hierarchy for a company and outline how their data is structured. All companies have top level dimensions called Account, Scenario, Departmen...
Cube Planning Drilldown API
The Drilldown API from Cube Planning — 1 operation(s) for drilldown.
Cube Planning ERP API
The ERP API from Cube Planning — 4 operation(s) for erp.
Cube Planning Events API
This endpoint can be used to track generic events completed by users.
Cube Planning Formulas API
Cube uses formulas to calculate values for a dimension, based on other dimensions. Examples: - Gross Margin = "Revenue" - "Cost of Goods Sold" - Net Income = "Gross Margin" - "E...
Cube Planning Integrations API
The Integrations API from Cube Planning — 7 operation(s) for integrations.
Cube Planning Invitations API
The Invitations API from Cube Planning — 3 operation(s) for invitations.
Cube Planning Library API
The Library API from Cube Planning — 12 operation(s) for library.
Cube Planning Notifications API
The Notifications API from Cube Planning — 2 operation(s) for notifications.
Cube Planning Permissions API
The Permissions API from Cube Planning — 2 operation(s) for permissions.
Cube Planning permissionsets API
The permissionsets API from Cube Planning — 2 operation(s) for permissionsets.
Cube Planning PlanModeSessions API
The PlanModeSessions API from Cube Planning — 1 operation(s) for planmodesessions.
Cube Planning Planning Table API
The Planning Table API from Cube Planning — 4 operation(s) for planning table.
Cube Planning Scenarios API
The Scenarios API from Cube Planning — 1 operation(s) for scenarios.
Cube Planning Tags API
Alternative hierarchies & grouping of dimensions in Cube
Cube Planning Taskflow API
The Taskflow API from Cube Planning — 11 operation(s) for taskflow.
Cube Planning Team API
The Team API from Cube Planning — 1 operation(s) for team.
Cube Planning User API
User endpoints allow for various functionality tied to users.
Cube Planning UserCompanies API
The UserCompanies API from Cube Planning — 3 operation(s) for usercompanies.
Cube Planning Workflow API
The Workflow API from Cube Planning — 5 operation(s) for workflow.
Scroll within the panel for all 42 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
cube-planning-mcp.yml
MCP SERVERSecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Cube Planning — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
Pagination, idempotency, versioning, errors, and events
Access & Security 5
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/cube-planning · machine-readable index on apis.io