Legal
Developer API Terms
The terms for the developer API at studio.blockoutgames.com/developer/v1 and the game keys that open it.
Last updated
These terms cover the developer API (studio.blockoutgames.com/developer/v1) and, once it opens, the MCP server at mcp.blockoutgames.com. They add to the Terms of Service and the Acceptable Use Policy. The developer docs explain how the API works.
Game keys
Who gets one. Each studio game has at most one key in use. It is created, rotated and revoked by the game's crew and the studio's owners, on the game's Developer tab in the studio.
What it opens. A key reads the market data the API serves and posts player feedback for its own game. It opens nothing else: not the studio, not another game's feedback, not anyone's account.
Keeping it secret. The key is shown once. Store it only as the experience's Roblox secret
BlockoutApiKey, for the domainstudio.blockoutgames.com. Never put it in source code, in a place script, on a client, in a message or in a repository. We keep only a hash of it, so we cannot show it to you again.If it leaks. Rotate it at once on the Developer tab, and tell us at [email protected]. You are responsible for calls made with your game's key until it is rotated or revoked.
Rate limits and fair use
Each key may make 120 requests a minute, and all keys together 1,200. Each network address may make 1,200 reads and 240 writes a minute. A request body is at most 16 KiB and a feedback message at most 2,000 characters. A request over a limit is refused with 429 and a time to wait; wait it out instead of retrying at once. The errors and limits page has the details, and it wins if it is more recent than this page.
The limits protect the studio's budget with Roblox, which the data collection shares. Do not work around them with several keys, addresses or accounts, and do not ask for the same data more often than it changes.
What you may build
You may use the API in the studio's Roblox experiences: to show the market to players, to build games about it, and to collect feedback from players. You may not resell the data, offer it as a data feed or a competing service, use it to identify or track individual players, or use it in any way Roblox's own terms forbid.
Feedback you post may hold a player's Roblox user id and their words. Post only what players chose to send, tell them it goes to the studio, and follow Roblox's rules on player data. The Privacy Policy says how the studio keeps it.
Attribution
Where an experience shows players the market data, say it comes from Blockout Games. Experiences built from the Roblox Template must also show the "Powered by Blockout Games" attribution its licence requires. Do not suggest that Blockout Games or Roblox Corporation endorses your experience.
Changes and revocation
We may change the API, its limits or these terms; breaking changes are listed in the changelog. We may revoke a key, or refuse requests from an address, if it breaks these terms, puts the service or the studio's Roblox budget at risk, or the law requires it. A game's crew can revoke its own key at any time.
No warranty
The API and its data are provided "as is", with no promise of availability, accuracy or fitness for a purpose, to the extent the law allows. The data can be wrong or late (see Data shown "as is"), and is not financial advice. The status page shows whether the API is up.
Changes
28 October 2026: first version.



