What your AI can do

Connect Roblox Open Cloud safely

An optional, beginner-safe setup that lets the agent publish a saved place file, read place versions, and read analytics, using a throwaway game and a minimum-permission key.

Optional · about 15 minutes. You do not need an Open Cloud key for normal Bricklayer use. Set this up only if you want the agent to publish a saved place file, read place versions, or read experience analytics.

Use a throwaway game, not your real game

An API key acts like a password. Make a new private Baseplate named Bricklayer Open Cloud Test, publish it as a new private experience, then use File → Save to File to make a fresh .rbxl copy. You can delete the experience and key after this test.

Step 1: Create the smallest possible key

Open API Keys

Open Creator Dashboard → API Keys.

Create and name the key

Choose Create API Key and name it Bricklayer disposable test.

Restrict it to the test experience

Turn on Restrict by Experience and select only your new test experience.

Add only three permissions

Add only the three permissions below. Do not choose “all experiences” or extra operations.

Permission	Why
`universe-places:write`	Publish the saved test-place file
`universe.place:read`	Read recent versions of the test place
`universe.analytics:read`	Read aggregate analytics for the test experience

Pick a short expiration

Choose a short expiration such as one day if Roblox offers it. Leave IP restriction off if you do not have a fixed IP.

Generate and copy the key

Choose Save & Generate key, then copy the key once. Roblox may not show the full secret again.

Never paste the key into AI chat, a tool call, a project file, Git, or a screenshot. Bricklayer reads it only from the local process that you launch below.

Step 2: Quit Bricklayer, then launch it with the key

Completely quit Bricklayer Editor first. Choose your computer:

macOS

Open Terminal (⌘ Space → type Terminal → Return), paste all four lines, and press Return. Paste the key when asked; it stays invisible while you paste.

read -s "BRICKLAYER_ROBLOX_API_KEY?Paste your Roblox key, then press Return: "
echo
open -na "Bricklayer Editor" --env "BRICKLAYER_ROBLOX_API_KEY=$BRICKLAYER_ROBLOX_API_KEY"
unset BRICKLAYER_ROBLOX_API_KEY

Windows

Open Windows PowerShell from the Start menu, paste the whole block, and press Enter. Then paste the key when asked; it stays hidden while you paste.

$key = Read-Host "Paste your Roblox key, then press Enter" -AsSecureString
$pointer = [Runtime.InteropServices.Marshal]::SecureStringToBSTR($key)
try {
  $env:BRICKLAYER_ROBLOX_API_KEY = [Runtime.InteropServices.Marshal]::PtrToStringBSTR($pointer)
  Start-Process "$env:LOCALAPPDATA\Programs\Bricklayer Editor\Bricklayer.exe"
} finally {
  [Runtime.InteropServices.Marshal]::ZeroFreeBSTR($pointer)
  Remove-Item Env:BRICKLAYER_ROBLOX_API_KEY
}

Step 3: Try the tools on the test game

Keep the same disposable place open in Studio. Send these requests one at a time:

Publish the saved copy

“Use bl_publish_place with versionType set to published. Use this file: /full/path/to/Bricklayer-Open-Cloud-Test.rbxl.” Check the test-game name and file path on the approval card before allowing it.

Read recent versions

“Use bl_place_versions with a limit of 5.” The version you just published should appear.

Read analytics

“Use bl_get_analytics for DailyActiveUsers with OneDay granularity.” A new private game will usually return no data; an empty result is okay.

Need the full file path?

On Mac, hold Option while right-clicking the file and choose Copy … as Pathname. On Windows, hold Shift while right-clicking and choose Copy as path.

When you are done: delete the key

Quit Bricklayer Editor, return to Creator Dashboard → API Keys, and disable or delete Bricklayer disposable test. Archive or delete the throwaway experience too. Never reuse the test key for a real game.