Forward-looking confidence intervals
Stochastic modeling is applied to historical volatility and volume data to produce a range of likely outcomes, rather than a single forecast figure, so you can weigh probability alongside magnitude.
Wavestravel aggregates order books, balances and historical data from multiple exchanges into a single dashboard, so you can assess exposure and liquidity without switching between platforms or reconciling spreadsheets by hand.
Figures shown for illustration only; actual values depend on connected accounts.
Wavestravel ingests order-book depth, historical price series, funding rates and account balances from each connected exchange through its public and authenticated APIs. Each feed is normalised to a common schema before analysis, which removes the reconciliation work that typically falls to an independent investor managing several accounts.
The dashboard presents these feeds as a single sortable table rather than a separate browser tab per exchange. Each row carries a timestamp and source label, so any figure can be traced back to its origin exchange.
Predictive outputs are presented as ranges and probabilities rather than single-point forecasts, consistent with how stochastic models should be interpreted.
Stochastic modeling is applied to historical volatility and volume data to produce a range of likely outcomes, rather than a single forecast figure, so you can weigh probability alongside magnitude.
Positions held across different exchanges are checked for concentration and correlation, flagging cases where apparent diversification is reduced by overlapping underlying assets.
Every data point carries a timestamp and source latency figure, so decisions can account for how current the underlying feed actually is rather than assuming it is live.
The workflow below reflects how most location-independent users check and act on their data, typically once or twice per working day.
Add exchange API keys with read-only scope where the exchange supports that distinction. No withdrawal permission is requested at any stage.
Open the dashboard from any browser to review balances, exposure and latency-flagged data, regardless of which country or time zone you are working from.
Wavestravel does not place trades automatically. Every recommendation is logged alongside the data it was based on, so the decision and its rationale remain yours to review.
A dense, factual view of what is tracked and how often it updates, intended for users who want to verify the basis of any figure before acting on it.
| Metric | Update frequency | Source type |
|---|---|---|
| Spot order book depth | Near real-time, per polling interval | Public API |
| Historical OHLCV series | Daily batch, or on demand | Public API |
| Account balances | Real-time on request | Authenticated API (read-only) |
| Open position sizing | Real-time on request | Authenticated API (read-only) |
| Funding rate (perpetual contracts) | Per exchange schedule | Public API |
| API latency and uptime | Continuous monitoring | Internal telemetry |
API keys are stored encrypted and scoped to read-only access wherever the connected exchange allows that distinction to be enforced. Wavestravel does not request withdrawal or transfer permissions as part of standard account connection.
Yes. The dashboard is browser-based and does not require a fixed UK location or IP address to sign in. Access depends on your login credentials, not your physical location at the time.
The dashboard displays the last successfully retrieved data point with its original timestamp, and marks the row as stale until the connection is restored. No figure is silently updated without a corresponding timestamp.
No. The platform is read-only with respect to trading activity. It presents aggregated data and modeled ranges; any order placement remains a manual decision made outside the dashboard.
Wavestravel supports a range of major spot and derivatives exchanges that expose public and authenticated APIs. A current integration list is maintained in the documentation, since supported endpoints change as exchanges update their own API terms.
Keys are stored encrypted at rest and are used only to retrieve the data categories described in the documentation. Where an exchange allows scoped, read-only keys, Wavestravel requests only that scope.
Have a question not covered here? Contact the support team.
Provide a work email to receive setup instructions and a documentation link for connecting your first exchange account.
No credit card required to review documentation. Read-only API connection only.