Skip to content

Research directory

BTCMox developer resources

Integrate documented calculations and permitted market observations through authenticated server requests. Access is provisioned after an agreed paid arrangement.

Tools and working views

12 related resources. Choose the measurement you need, then read the assumptions on its page.

Funding APR vs Return on Capital: A Bitcoin Hedge Example | BTCMoxSeparate annualized funding on notional from return on committed capital. Work through a spot-perpetual example including fees and margin reserves.Open resource ↗BTCMox Calculation Methodology & AssumptionsUnderstand BTCMox calculator units, fee conventions, annualization, live-data labels, testing boundaries and the assumptions behind each scenario.Open resource ↗BTCMox Data Sources, Providers & Access LimitationsReview BTCMox public API providers, timestamp conventions, browser data sharing and the limitations of spot, funding, network and stablecoin observations.Open resource ↗TradingView Webhook Payload Builder and Validator | BTCMoxBuild and validate a local TradingView-style JSON alert payload with an event ID, timestamp, symbol, side and notional. Export the payload for your own system.Open resource ↗Market API cache age and source timestamps | BTCMoxResponse receipt time tells you when a system received data. Source time tells you when the provider says the observation was made, when that field exists. Cache age adds another distinct delay.Open resource ↗BTCMox API: Crypto Calculations and Controlled Data AccessA documented API for crypto scenario calculations and operator-enabled market adapters. Learn about manual access, authenticated requests and data limits.Open resource ↗BTCMox API Documentation: Authentication, JSON and EndpointsIntegrate BTCMox v1 calculations and licensed market routes with header authentication, strict JSON inputs, account limits and explicit source timestamps.Open resource ↗BTCMox API Access: Manual Quotes, Quotas and RenewalUnderstand the BTCMox API manual quote and invoice workflow, calculation and research access, request allowances, expiry and operator-issued keys.Open resource ↗BTCMox API Status: Check This DeploymentCheck the current BTCMox API health response without an API key. Understand database health, upstream-provider limits and meaningful availability errors.Open resource ↗BTCMox API Data Methodology: Quotes, Candles and AssumptionsRead the BTCMox API conventions for venue quote units, snapshot timestamps, candle completeness, cache ages, visible depth and six financial scenarios.Open resource ↗BTCMox API Acceptable Use: Keys, Quotas and Data RightsUse BTCMox API access within the agreed plan, protect credentials, respect quotas and provider rights, and keep research outputs separate from execution.Open resource ↗BTCMox API Privacy: Credentials, Usage Counters and InputsUnderstand what the BTCMox API stores for keys and usage, how scenario inputs are handled, what providers receive and where to contact the operator.Open resource ↗

A practical research sequence

Start with the question you need to answer: available liquidity, total cost, collateral sensitivity, protocol activity or portfolio exposure. Choose a tool whose input units and data source match that question. Capture the observation time and compare a baseline before changing assumptions.

Each working view links to its methodology and related tools. The public market pages load named providers automatically; local scenario and CSV tools calculate in the browser. Pausing public feeds freezes observations in the current tab, so recheck timestamps before using a retained result.

Interpretation and boundaries

Integrate documented calculations and permitted market observations through authenticated server requests. Access is provisioned after an agreed paid arrangement.

The catalogue includes distinct calculations and data views rather than a claim that every measurement is a trading signal. A computed ratio can be numerically correct while its assumptions no longer match the market. Use the source references, check missing fields and retain enough context to reproduce the result.