CUBE / 03 · YOUR STORE API
Your store.
Your data.
Connect your website, collect session samples, and estimate each visitor’s buying chance.
Loading your account…
GET CONNECTED
One account. Your own API.
Sign in or create a Neurvance account, subscribe with Stripe, and create your API key after payment is verified. Each subscription includes a maximum of 1,000 API calls per hour per account.
Sign in or create an account ↗01 / SUBSCRIPTION
Cube monthly
Maximum 1,000 API calls per hour per account. Shared across all sessions and API endpoints in a rolling 60-minute period.
Read before subscribing. Cube 1.0 is governed by the Terms of Use, Privacy Policy, and Data Protection Addendum.
Collect sessions and request buying estimates with an active subscription. Cancel anytime; API access continues until the paid period ends. Predictions require 500 completed sessions or usable legacy 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 preserves your account data.
04 / PREDICTION READINESS
Collecting enough history.
Collect completed sessions or usable legacy rows. The readiness score updates continuously and reaches 100% at 1,000 rows.
INTEGRATION
Connect from your website server.
Observe visitors every ten seconds and send one account-wide batch every minute with POST /api/v1/batch. Include starts, ordered samples, lifecycle events and requested calculations. Keep queues in RAM until acknowledgment and honor Retry-After. A minute scheduler uses about 60 normal batches plus up to 20 urgent calls or retries per hour, leaving most of the 1,000-call hourly limit as headroom. Batches are limited to 64 KiB, 20 sessions and 120 observations. Batching requires updating your server integration; existing endpoints below remain available. Preserve entry time, the six-hour deadline, checkout protection and five-second navigation grace. Completed observations become weighted merged statistics; finalized outcomes cannot change.
Your secret websiteID is shown once when you create or rotate it above. There is no separate public websiteID to copy.
POST /api/v1/savedata
Authorization: Bearer YOUR_SECRET_WEBSITEID
Content-Type: application/json
{
"websiteID": "YOUR_SECRET_WEBSITEID",
"session_id": "unique-visitor-session",
"sample_seq": 1,
"captured_at": "2026-09-10T14:30:00Z",
"visitor_id": "your-visitor-id",
"data": {
"avgSpeed": 120, "mouseClicksTotal": 12,
"colorsSeen": ["blue"], "productsSeen": ["cup", "vase"],
"productsviews": 4,
"productsSold": 0, "productsClicked": 3,
"mouseSide": "left", "mouseUpsideDown": "up",
"time": 10, "temperature": 20,
"rain": false, "day": "Monday",
"lastBought": null, "lastBoughtItem": ""
}
}Retry the same sample sequence and payload to avoid duplicate rows. Only labeled sessions appear in your CSV.
Finish the session
POST /api/v1/sessions/complete
{"websiteID":"YOUR_SECRET_WEBSITEID","session_id":"unique-visitor-session","last_sample_seq":12,"boughtNumber":3}Send the total number of products, not money spent. Confirm completion only after delivering every sample.
Ask for a prediction or optimization
POST /api/v1/perbuy
POST /api/v1/optimizechance
POST /api/v1/recommendproducts
POST /api/v1/spendmoretime
{"websiteID":"YOUR_SECRET_WEBSITEID","session_id":"unique-visitor-session"}Use the same Bearer key and active session for all four calculations, or include them in a scheduled batch. Quantity is expected products across all visits; optional reliability reports independent support and uncertainty. Optimization returns an empty recommendations list and spendmoretime returns an empty recommendation because store actions lack action-effect evidence. Product suggestions require five supporting sessions and return at most three products. Never evaluate response strings as code. Controlled synthetic benchmarks do not prove real-store accuracy or sales uplift.