Generic expected value
API · /casino-api
Casino Odds API
Casino game maths as an API, computed locally and deterministically — exact house edge, expected value and return-to-player, never a simulation. The roulette endpoint takes a wheel variant (European single-zero or American double-zero) and a bet type (straight, split, street, corner, six-line, column, dozen, red/black, odd/even, high/low, or the American basket) and returns the win probability, the payout, the expected value per unit staked and the house edge — the famous 2.70 % on every European bet, 5.26 % on American (7.89 % on the basket), and 1.35 % when the European la-partage rule is applied to even-money bets. The craps endpoint gives the exact 36-outcome dice maths for the pass line (1.41 %), don't pass (1.36 %, with its 12-push), the field (2.78 % when 12 pays 3:1) and any seven (16.67 %). The bet endpoint is fully generic: give any win probability and payout and it returns the expected value, house edge, return-to-player and the standard deviation of a unit bet — perfect for keno, slots, scratch cards or a custom wager. Everything is computed locally and deterministically, so it is instant and private. Ideal for gaming-analytics, responsible-gambling, casino-education and odds-comparison app developers, advantage-play and bankroll tools, and probability teaching. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. This is the game-odds maths; for Texas Hold'em hand equity use a poker API and for converting betting prices use an odds API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 89 ms
- Server probes · 24h
- Subscribers
- 3,692
- active
- Total calls
- 36
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 4,450 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 4,450 calls/month
- 2 req/sec
- Roulette + craps + generic EV
- No credit card
Starter
€4.45 /month
- 47,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 47,000 calls/month
- 6 req/sec
- House edge, RTP, standard deviation
- Email support
Pro
€12.40 /month
- 228,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 228,000 calls/month
- 15 req/sec
- Gaming-analytics & bankroll pipelines
- Priority support
Mega
€38.50 /month
- 1,270,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,270,000 calls/month
- 40 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Craps Odds API
Craps odds maths as an API, computed locally and deterministically and exactly — the dice probabilities behind the table, derived from the 36 ways two dice fall, not pulled from a chart. The come-out endpoint gives the come-out roll: the pass line wins on a 7 or 11 (8 of 36, 22.2 %), loses on craps 2, 3 or 12 (4 of 36, 11.1 %), and otherwise sets a point (24 of 36, 66.7 %). The point endpoint gives the odds of making a point before a seven — probability = ways(point) ÷ (ways(point) + 6) — so a 6 or 8 makes 45.5 % of the time and a 4 or 10 only 33.3 %, with the TRUE odds (2:1, 3:2, 6:5) the free odds bet behind the line pays at zero house edge. The bet endpoint gives the house edge of the main bets: the line bets at 1.41 % (pass) and 1.36 % (don't) and place 6/8 at 1.52 % are the table's best, while place 4/10 (6.67 %), the field and proposition bets like any seven (16.67 %) bleed you. Everything is computed locally and deterministically, so it is instant and exact. Ideal for craps and casino-game apps, gambling-education and odds tools, game-design back-ends, and probability teaching. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Educational — not betting advice; back the line with free odds.
api.oanor.com/craps-api
Roulette Odds API
Roulette odds maths as an API, computed locally and deterministically and exactly — the payout, the true probability and the house edge behind every bet, the numbers a fair game tells you and a casino would rather you ignore. The payout endpoint gives a bet's payout, winning numbers, win probability and house edge for a European (single-zero) or American (double-zero) wheel: a straight-up number pays 35 to 1 but wins only 1 in 37, an edge of 2.70 % European or 5.26 % American, the same on almost every bet because the payout simply ignores the zeros. The expected-value endpoint turns a stake into its expected value — stake × (win probability × (payout + 1) − 1), always negative and equal to minus the stake times the house edge — so €10 on a single number on a European wheel is worth −€0.27 every spin. The martingale endpoint exposes the doubling system: total risked = base × (2^steps − 1), the bet that explodes after a losing streak, and the bust probability — proof on the maths that no progression beats the zero. Everything is computed locally and deterministically, so it is instant and exact. Ideal for casino-game and odds apps, gambling-education and responsible-play tools, game-design back-ends, and probability teaching. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Educational — not betting advice; the house always wins long-run.
api.oanor.com/roulette-api
Blackjack Strategy API
Blackjack maths as an API, computed locally and deterministically and exactly — the hand value, the textbook basic-strategy play and the dealer odds, the numbers that hold the house edge to half a percent. The hand-value endpoint scores a hand the way the table does: aces count 11 unless that busts, then 1, so it reports the best total, whether it is soft (an ace still counting 11, safe to hit) or hard, whether it busts, and whether two cards make a blackjack. The strategy endpoint gives the correct basic-strategy action — hit, stand, double or split — for any hand against the dealer's upcard, for the standard 4-to-8-deck game where the dealer stands on soft 17 with double-after-split allowed: 16 against a 10 hits, a pair of 8s always splits, soft 18 doubles against a 6 but hits against a 9, and 11 doubles against everything but an ace. The dealer-odds endpoint gives the dealer's bust probability by upcard — a 5 or 6 busts about 42 % of the time, an ace only 12 % — the reason you stand on stiffs against weak upcards. Everything is computed locally and deterministically, so it is instant and exact. Ideal for blackjack trainers and strategy apps, card-game and casino-game tools, learning aids, and game back-ends. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Educational — not betting advice; the house always keeps an edge.
api.oanor.com/blackjack-api
Screw Auger API
Screw-conveyor and grain-auger maths as an API, computed locally and deterministically — the capacity, speed and throughput numbers a farmer, millwright or material-handling engineer sizes an auger with. The capacity endpoint gives the volumetric throughput from the screw geometry: the annular flight volume per turn ((π/4)(diameter² − shaft²) × pitch) × rpm × 60 × the trough loading, so a 9-inch full-pitch screw on a 2.5-inch shaft at 40 rpm and 45 % loading moves about 330 cubic feet — 265 bushels — an hour. The speed endpoint inverts it, the rpm needed for a target capacity, so you don't overspeed a small auger and grind the grain. The bushels endpoint converts a volumetric rate to bushels and tons per hour (1 bushel = 1.2445 ft³, tons = bushels × test weight ÷ 2000), so 330 ft³/hr of 56-lb corn is 265 bushels or 7.4 tons an hour — the number you match to the dryer or the truck. Everything is computed locally and deterministically, so it is instant and private. Ideal for grain-handling and ag-equipment apps, material-handling and conveyor-design tools, farm-build calculators, and engineering aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — incline and material change real throughput. For belt conveyors use a conveyor API.
api.oanor.com/auger-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Casino Odds API?
What's the rate limit for Casino Odds API?
How much does Casino Odds API cost?
Can I cancel my subscription anytime?
Is Casino Odds 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/casino-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/casino-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/casino-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/casino-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.