The Server Intelligence API: live Roblox server data for developers
The Server Intelligence API is a tiered REST API for live Roblox server, discovery, trend, and forecast data — with scoped keys, per-call metering, and signed webhooks. Here's what it exposes and how to build on it.
The Server Intelligence API is a tiered REST API that gives developers live Roblox server, discovery, trend, and forecast data over authenticated HTTP — with scoped API keys, per-call usage metering, and signed webhooks for usage and billing events. If you are building a tool that needs to know which servers are healthy, which games are rising, or where demand is heading, it is the data layer for it.
What it exposes
- →GET /v1/servers/find — the best live servers for a game, ranked by quality and fill.
- →GET /v1/servers/stats — occupancy and health for a specific server.
- →GET /v1/discovery/search — quality-ranked game search.
- →GET /v1/discovery/recommendations — "games like X" vector recommendations.
- →GET /v1/trends/top-games — trending and top games by genre.
- →GET /v1/forecasts/occupancy — predicted demand by region.
Built like real infrastructure
Every response includes a credits_used field so you can reconcile usage exactly against your invoice, and rate-limit headers so you can back off cleanly. Keys are scoped with least privilege and shown once at mint. Outbound webhooks are signed and SSRF-guarded before they leave us, and every privileged action is written to an audit trail. Billing is idempotent and metered per call, with monthly invoices and predictable overage.
Plans and limits
The Free tier gives 1,000 calls a month at 60 requests per minute over server data — enough to prototype. Dev raises that to 100,000 calls and adds discovery data; Pro reaches 1,000,000 calls at 600 requests per minute with trends and analytics included, and the lowest overage rate. You start on a free key and grow into a plan as your integration does.
Every call returns credits_used and rate-limit headers. You should never have to guess what an integration costs or when to back off.
Getting started is a curl away: mint a key, set it as a bearer token, and call an endpoint. The interactive reference lets you try every route with your own key before you write a line of code.