In the Roblox Creator Dashboard, navigate to your experience's Open Cloud settings and create an API key with DataStore read and/or write permissions scoped to the specific universe ID.
Identify your universe ID (shown in Creator Dashboard) and the DataStore name you want to access — these must match the DataStore used in your game scripts.
List DataStore entries with GET https://apis.roblox.com/datastores/v1/universes/<UNIVERSEID>/standard-datastores/datastore/entries?datastoreName=<NAME> using header x-api-key: <API_KEY>.
Read a specific entry with GET .../entries/entry?datastoreName=<NAME>&entryKey=<KEY>; the response body is the raw serialized value.
Write or update an entry with POST .../entries/entry?datastoreName=<NAME>&entryKey=<KEY> with the value as the request body and Content-MD5 header (base64-encoded MD5 of the body) for integrity verification.
Delete an entry with DELETE on the same URL pattern — deletions are soft-deletes and the entry remains listable for a retention period.
Known gotchas
Open Cloud API keys are separate from Roblox OAuth app credentials — they are created per-experience in Creator Dashboard and cannot be used for user-facing OAuth flows.
The Content-MD5 header is required for write operations; omitting it or providing an incorrect value results in a 400 error — compute it as the base64 encoding of the MD5 hash of the raw request body bytes.
DataStore keys written from in-game Lua scripts are accessible via Open Cloud using the same universe ID and store name, but versioning behavior (GetVersionAsync) is not fully exposed in all Open Cloud API tiers — check current API docs for version listing support.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp