CUBE / 03 · YOUR STORE API
Your store.
Your data.
Connect your website, send visit data, add your products, and estimate each visitor’s buying chance.
Loading your account…
GET CONNECTED
One account. Your own API.
Use your existing Neurvance account and the credits shared with Mindmap and AI widgets. Create your API key when access is available.
Sign in or create an account ↗01 / SUBSCRIPTION
Cube monthly
Read before subscribing. Cube 1.0 is governed by the Terms of Use, Privacy Policy, and Data Protection Addendum.
Send visit data and ask for commands and buying estimates with an active subscription. Cancel anytime; API access continues until the paid period ends. Predictions require 1,000 saved rows.
02 / SECRET WEBSITEID
A direct connection.
No API key yet
Your websiteID is your secret API key. Save this one credential as SHOP_WEBSITE_ID on your server. Only one credential can be active. Rotation replaces it immediately and keeps your saved data and products.
Checking whether key rotation is available…
04 / PREDICTION READINESS
Collecting enough history.
Predictions start at 1,000 saved rows (70%). The readiness score updates continuously and reaches 100% at 2,000 rows.
INTEGRATION
Connect from your website server.
Read the full setup guide ↗ Open the products page ↗
Every ten seconds, your server sends the visit’s six numbers with POST /upload. Add your products (name, bio and price) on the products page, then ask POST /main for layout commands and the best product, and POST /perbuy for the buying chance. Every call uses HTTPS and your secret websiteID as the Bearer key.
Your secret websiteID is shown once when you create or rotate it above. There is no separate public websiteID to copy.
POST /upload
Authorization: Bearer YOUR_SECRET_WEBSITEID
Content-Type: application/json
{
"bought_number": 0,
"avgSpeed": 120,
"avgCordinates": [640, 360],
"productsSeen": 6,
"productsClciked": 2,
"clicks": 14
}Send bought_number as the number of products bought, not money spent, and only after your server has verified the payment.
Ask for commands and the best product
POST /main
{"shown":"BIO_OF_THE_PRODUCT_ON_SCREEN","currentlyDoing":{"speed":120,"clicks":14,"clicked":2,"productsSeen":6}}Returns commands (moreProducts() / lessProducts()), spendMore and best (the bio of the product to feature, or null).
Ask for the buying chance
POST /perbuy
{"currentlyDoing":{"speed":120,"clicks":14,"clicked":2,"productsSeen":6}}Until your website has 1,000 saved rows, both calls answer with a message instead of a prediction. Never evaluate response strings as code.