Rank the universe from most trending to most mean-reverting
API · /hurst-api
Hurst Exponent & Market Regime API
Tells you whether each market is trending, behaving like a random walk, or mean-reverting — the single most important thing to know before choosing a strategy — computed live from Yahoo Finance daily closes, no key, nothing stored. A trend-following system bleeds money in a mean-reverting market, and a fade-the-move system gets run over in a trending one; the Hurst exponent (via rescaled-range R/S analysis) measures which world you are in. A Hurst above ~0.55 means the series is persistent — moves tend to continue, so it trends and trend-following fits; near 0.5 it is a random walk with no edge either way; below ~0.45 it is anti-persistent — moves tend to reverse, so it mean-reverts and fading extremes fits. Alongside it the API returns the Kaufman Efficiency Ratio (net move divided by the total path travelled, 0 = pure noise, 1 = a perfectly straight trend), a second intuitive read on how cleanly a market is trending. The asset endpoint returns one instrument's Hurst, efficiency ratio and a regime label; the screener endpoint ranks the cross-asset universe (equities, sectors, commodities, bonds, FX and crypto; filterable by class) from most trending to most mean-reverting. This is the persistence / trend-versus-mean-reversion regime cut — distinct from the z-score stretch gauges (how far a price is from its average right now, not the structure of its moves), the multi-timeframe momentum-alignment API and the price APIs. It tells you which kind of strategy the market is paying for.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 200 ms
- Server probes · 24h
- Subscribers
- 4,825
- active
- Total calls
- 0
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 670 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 670 calls/month
- 2 req/sec
- All endpoints
- No credit card
Starter
€12.50 /month
- 14,100 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 14.1k calls/month
- 6 req/sec
- All metrics & classes
- Email support
Pro
€38.60 /month
- 79,000 calls / month
- 16 requests / second
- Hard cap (429 above quota, no overage)
- 79k calls/month
- 16 req/sec
- Priority support
Mega
€85.80 /month
- 458,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 458k calls/month
- 40 req/sec
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Precious-Metal Ratios API
The ratios between gold, silver, platinum and palladium, where they sit in their own multi-year history, and which metal is cheap relative to which — computed live from Yahoo Finance futures, no key, nothing stored. A precious-metal price tells you what an ounce costs; the ratio between two metals tells you which is expensive relative to the other — and these ratios are famously mean-reverting, which is why the gold/silver "mint ratio" is one of the oldest trades there is: when it stretches to an extreme, traders rotate from the dear metal into the cheap one and ride it back. A single current ratio is only half the story; what matters is where that ratio sits in its multi-year range. This API computes the gold/silver, gold/platinum, platinum/palladium, gold/palladium and silver/platinum ratios, and for each returns its current value, its percentile within a multi-year window (the context that turns a number into a signal), the window min/max/average, and a plain-language rotation read — at a high percentile the numerator metal is historically expensive (favour the denominator), at a low percentile the reverse. The ratios endpoint returns the whole complex; the ratio endpoint returns one pair with its component prices; the history endpoint returns the ratio time series. This is the precious-metal-ratio / mean-reversion cut — distinct from the inter-commodity crack/crush spread API (which gives the current gold/silver ratio but no history, percentile or signal), the intermarket-ratio board and the metals spot-price feed. It is the ratio with its history attached.
api.oanor.com/preciousratios-api
Variance Ratio Test API
A formal statistical test of whether a market follows a random walk, or whether its returns carry tradeable momentum or mean-reversion that is real rather than noise — the Lo-MacKinlay variance ratio test, computed live from Yahoo Finance daily closes, no key, nothing stored. Most persistence tools give you a single descriptive number; this gives you a hypothesis test with a verdict. The variance ratio compares the variance of multi-day returns to the variance of one-day returns scaled up: under a true random walk the ratio is 1 at every horizon. A ratio above 1 means returns positively autocorrelate (trends persist — momentum); below 1 means they reverse (mean-reversion). Crucially it attaches a heteroskedasticity-robust z-statistic and a p-value at each horizon, so you know whether the deviation from a random walk is statistically significant or just sampling noise — the thing a point estimate cannot tell you. The asset endpoint runs the test at horizons of 2, 4, 8 and 16 days and returns each ratio, z-statistic, p-value and a reject/fail-to-reject verdict, plus an overall read. The screener endpoint ranks the cross-asset universe by their 2-day variance ratio, separating the statistically momentum-like markets from the mean-reverting ones. This is the random-walk hypothesis-test cut — distinct from the Hurst-exponent regime API (a point estimate with no significance), the momentum and the price APIs. It is the test, with the p-value attached.
api.oanor.com/varianceratio-api
Streak Analysis & Reversal Odds API
The consecutive up- and down-day runs swing-traders fade, with the historical probability that a run reverses, computed live from Yahoo Finance daily closes — no key, nothing stored. "It has gone up five days in a row, it is due a pullback" is a guess until you put a number on it. This API counts every up- and down-day run in an instrument's history and measures, for each run length, how often the very next day reversed it — turning a gut feeling into a base rate. For each instrument it returns the current streak (its direction and length), the longest up and down streaks in the window, the average run length, the full distribution of run lengths, and the reversal table: after k consecutive up (or down) days, the share of times the next day went the other way, with the sample size behind each figure. If a name is currently on a streak it also returns the historical odds that tomorrow reverses it — the one number a mean-reversion trader wants. The asset endpoint returns one instrument's full streak profile; the screener endpoint ranks the universe by how stretched each is right now (current streak length), so you can see what is most extended. This is the consecutive-run / reversal-odds cut — distinct from the Hurst persistence-regime API, the multi-timeframe momentum API, the candlestick-pattern API and the price feeds. It is the runs, counted, with the odds attached.
api.oanor.com/streak-api
Crypto Pairs Trading & Spread API
The statistical-arbitrage signal between two coins — how stretched their price ratio is versus its own recent average, computed live from Binance daily candles (no key, nothing stored). Pairs traders do not bet on direction; they bet on the spread between two correlated coins reverting to its mean. When ETH/BTC (or any ratio) runs two standard deviations above its average, the spread is stretched — short the rich leg, long the cheap one, and profit when it snaps back. The spread endpoint takes two coins and returns the current price ratio, its rolling mean and standard deviation, the z-score (how many standard deviations stretched), the return correlation of the two coins (pairs trading works on correlated pairs) and a long/short mean-reversion signal. The screener endpoint scans every pair in a liquid basket and ranks them by absolute z-score — the most stretched, most tradeable spreads right now. The coins endpoint lists what is covered. The pairs-trading / relative-value spread cut for crypto — distinct from the correlation-&-beta API (which gives the correlation matrix, not the tradeable spread), the single-coin momentum, the funding-arbitrage and the price APIs. It answers whether a spread is stretched, not whether two coins move together.
api.oanor.com/cryptopairs-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Hurst Exponent & Market Regime API?
What's the rate limit for Hurst Exponent & Market Regime API?
How much does Hurst Exponent & Market Regime API cost?
Can I cancel my subscription anytime?
Is Hurst Exponent & Market Regime API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/hurst-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/hurst-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/hurst-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/hurst-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.