QubeHub.ai

For engineers and integration partners

Build on QubeHub.

Connect your website, ERP, BI tools and AI assistants to the same live inventory, leads and deals your sales team works from.

Six ways in.

REST API

Partner Data API

Read and write your catalog from outside QubeHub: projects, units, building structure and media, plus read access to leads, deals and agents. Sync from an ERP or a website by your own external IDs.

An admin issues a key in Settings → API Keys → Internal API keys and picks its scopes, such as units:read or units:write.

Check an API key
curl https://<your-tenant-host>/api/data/v1/whoami \
  -H "X-Internal-Key: <your-api-key>"

Returns the key’s scopes, your base URL, rate limits and the OpenAPI reference at /data-api-docs/swagger.json.

Partner Data API guide

Events

Webhooks

Get an HTTP POST every time a lead, deal, contact, unit, project or agent is created, updated or deleted. Point it at your marketing CRM, ERP or BI pipeline and subscribe only to the events you need.

Each delivery keeps the same X-Delivery-Id across retries, so you can deduplicate safely. Failed deliveries are retried with increasing backoff.

Signature header
X-Signature-256: t=<unix-seconds>,v1=<hex>
v1 = HMAC-SHA256(secret, "<t>.<raw body>")

Sent when the webhook has a signing secret. Recompute the HMAC over the raw body and reject stale timestamps to block replays.

Webhooks guide

Workflows

Automations

Describe a routine in plain words, like greeting a new lead, chasing a stale deal or sending the head of sales a nightly digest, and the AI author writes it in TypeScript against the qh.* SDK.

It runs when a record changes, on a schedule or when a webhook arrives, in an isolated sandbox with hard limits. You test it against scenarios before it goes live, and every run is logged so you can inspect and replay it.

Automations guide

Your website

Embeddable widgets

Put a live unit picker, the chessboard of your building, or a contact form on your own website with two lines of HTML. Unit picker leads land in your CRM with their context: buyer type and shortlisted units.

Create the embed in the CRM to get its snippet. The widget resizes itself and pushes its events to your dataLayer.

Embed snippet
<div data-qube-widget="unit-picker" data-embed="<embed-id>"></div>
<script src="https://<your-tenant-host>/embed/v1/loader.js" async></script>

The CRM fills in your embed ID and host.

Widget examples

AI assistants

MCP for Claude

Connect Claude, Claude Code or another MCP client that supports remote servers to your QubeHub workspace. A workspace admin first turns on AI assistants in Settings → AI assistants; then you sign in with your workspace and a one-time code sent to your email.

Claude then works with your CRM under your own role and permissions, and the connection can be revoked from the CRM at any time.

Add to Claude Code
claude mcp add --transport http qubehub https://mcp.qubehub.ai/mcp

In Claude, add the same URL as a custom connector.

Setup guide and Claude plugin

TypeScript

JavaScript SDK

A small, typed client for the Partner Data API v1, with a helper that verifies webhook signatures so you don’t have to write the HMAC check yourself.

Open source under the MIT license.

SDK on GitHub

How integrations stay safe.

How we protect your data
  • One workspace, one database

    Each QubeHub customer runs on its own database. An API key, a webhook or a widget embed only ever reaches the workspace that created it.

  • Scoped, revocable keys

    A key holds only the scopes an admin picked, can expire, is shown once and can be disabled or revoked. Its calls are attributed to the key, not to a person.

  • Signed webhooks

    Set a signing secret on a webhook and every request carries an HMAC-SHA256 signature over a timestamp and the body, so your endpoint can reject forged and replayed calls.

  • AI under your role

    Each MCP tool call is checked against the signed-in user’s CRM role when it runs. Claude never sees more than that person can.

Book a demo.

Tell us what you’re selling. We’ll build the demo around it.

Your QubeHub demo

What do you want to see first?

Pick your team’s top priority.

Nothing is saved until you book.

Choose a time →

Discuss a project

Write to us

Fill out the form and we’ll reply by email.

Book a call →

Pick a time on our calendar.

By submitting, you agree to our Terms of Service and acknowledge our Privacy Policy.

Your hub

Get your price.

Just a few fields. Your setup is attached.

Write to us

Fill out the form and we’ll reply with the price.

Book a call →

Pick a time on our calendar.

Your portfolio —
Billed as 40 units minimum

QubeHub starts at 40 units. Smaller portfolios are billed as 40.

By submitting, you agree to our Terms of Service and acknowledge our Privacy Policy.

We’ll send pricing for your setup within one business day.

QubeHub onboarding

From your portfolio to a live hub.

Your first project can launch on day one. Here’s how the rest rolls out.

You provide

  • Project and unit data
  • Current pricing and availability
  • Approved sales materials
  • Team and agent list
  • Access to the systems you want connected

QubeHub handles

  • Portfolio and data setup
  • Module configuration
  • Permissions and access
  • Team onboarding
  • Launch

How it goes

  1. Step 1: First project live

    Your first project is set up and launched.

  2. Step 2: Portfolio configured

    Projects, units, pricing and the modules you need are in place.

  3. Step 3: Team & channels connected

    Your team and agents get access. All channels are linked.

  4. Step 4: Everything live

    Your whole portfolio runs on QubeHub.

Standard onboarding: 1–14 days. Custom integrations are scoped separately.

Email QubeHub

Send us a note.

No call needed. We’ll reply by email.

By submitting, you agree to our Terms of Service and acknowledge our Privacy Policy.