Endpoints
The methods you will reach for first. Everything the cabinet does has one; the full list lives in the server's own index.
How a call looks
POST https://cloud-api.rockslab.io/bedrock.v1.CabinetService/<Method>, JSON in and out, Authorization: Bearer brk_…. Field names are camelCase. Fields left at their zero value are left out of answers: a missing boolean is false, a missing list is empty. See API tokens for a full example.
The usual suspects
| Method | Does | Cost |
|---|---|---|
GetMe | who you are, your organizations and roles | read |
ListMyClusters | the organization's clusters, with their state and doors | read |
BuildMyCluster | build a cluster — returns an operation | heavy |
GetMyOrgJobRuns | recent operations; filter by temporalWorkflowId to find the one a call started | read |
GetMyOperation | one operation by runId (run-…): status, steps, error code | read |
GetMyAvailability | machine types in stock per location, for a provider (hcloud) | read |
GetMyLimits | every limit, what is used, where the value comes from | read |
GetMyAgentTokenUsage | what your agent budget went on | read |
ListMyActivity | the audit log | read |
The complete list
There are about 140 more — every one the MCP server exposes. The server's index lists each tool with what it does and its cost class, generated from the code so it cannot drift: cloud-api.rockslab.io/mcp/llms.txt. Each MCP tool rockslab_<verb>_<noun> is one of these methods underneath.
Errors
A refused call comes back with a Connect error code and a sentence for a person. Over a limit it is resource_exhausted, and the message ends with a line a script can read without parsing English:
limit: code=infra.servers used=8 limit=10 adding=6 next=billing
next says the way on: plan (a larger plan), billing (ask for more), support, or owner.