
Keys live under You on the rail. Caps are 2 / 2 / 10 / 25 on Cyclops / Minotaur / Kraken / Behemoth.
We store a hash. A lost key has to be replaced, not recovered. Copy it when it is shown.

The key is shown once, on a lime panel. Copy it before you leave.
Scopes
A key does only what it was minted to do. Tick the scopes when you press New key; the first three are ticked for you.
A run that also files its results with
save_to_vault needs vault:write as well as run.
A call the key has no scope for is 403 insufficient_scope, and the message names the scope it needed. Scopes are fixed once a key is minted: a key that needs more is a new key. Mint it, move the integration over, then revoke the old one.
A browser session — the Workbench, or an MCP client you signed in to — holds every scope.
Expiry
A key can stop working on its own after 30, 90 or 365 days, or never (the default). Pick it when you mint the key; the keys page shows the date. An expired key is401 key_expired — mint a new one.
Address allow-list
A key can be limited to the addresses it will be used from: single addresses (203.0.113.7) or ranges (198.51.100.0/24, 2001:db8::/32), up to 20. A call from anywhere else is 403 ip_not_allowed, and the message says which address it came from. Leave the list empty to use the key from anywhere.
Who can mint a key
Every plan includes the API and MCP. Credits gate the work, not the door. Live and test keys are counted separately: minting a test key never takes a live key’s slot.
The rate limit is counted per key, across REST and MCP together, so one runaway script doesn’t take down the others. Above it sits an account ceiling of twice a single key’s rate, shared by every key and browser session you hold — minting more keys buys you more credentials to rotate and to give one machine each, not more throughput.
Every plan holds at least two keys so that a rotation can overlap: mint the replacement, cut the integration over to it, then revoke the old one. Nothing is ever offline.
Cyclops has no monthly credits, so a call that spends credits still needs a top-up first. Convert is free of credits on every plan. A test key spends nothing at all.
Test mode
A test key startsmm_test_. Press New key on mediamonster.app/keys and pick Test at the top of the form; scopes, expiry and the address allow-list work the same as on a live key. Test keys wear an orange Test chip in the list.
A test key goes through every check a live key does, with the same code: the file is fetched, sniffed and measured, the options are checked, the plan is checked, the steps are checked for order, and the prompt rules apply. What a live key would be refused, a test key is refused, with the same code. Then, instead of running:
- Nothing is charged.
credits_chargedis0, and no free-tool allowance is used. - No model is called. The run finishes at once.
- You get a stand-in file of the right kind. A skill that makes a picture hands back a small PNG, a video a one-second MP4, a recording a short WAV, a document a one-page PDF, and words a short line of text. A skill that hands back the kind of file it was given — captions, clean audio, remove silences — hands back the file you sent.
- The job or run is real. It has an id,
poll_urlandGET /api/v1/jobs/{id}or/runs/{id}answer, and every view of it says"test": trueand"livemode": false. - Webhooks are delivered. Signed the same, with
"livemode": falseon the event, so you can test the receiving end too. - Nothing is filed in the Vault.
save_to_vaultis checked, then answers with what would have happened:
403 test_mode_unsupported. Over MCP, the tools that only read work and the ones that change the Vault are refused the same way.
Direct uploads work with a test key. The upload is real — the bytes go to storage and are checked like any other — so you can build the whole upload-then-run flow; the run you pass its upload_id to is a test run, and spends nothing.
Test runs aren’t spend. They don’t appear in your Queue, and nothing comes off your balance.
Rate limits
Every response to a call with a key carries the key’s own per-minute bucket:
A
429 rate_limited carries them too, with X-RateLimit-Remaining: 0, and retry-after in seconds. The account ceiling isn’t in the headers; a 429 over it says so in its message.
Errors
See Errors.
Check the account
GET /api/v1/me needs the read scope.
Usage
Usage, at the foot of the keys page, opens mediamonster.app/keys/usage: requests, errors and credits by day for the last 30 days, a total for each key, and the last 7 days one request at a time — its status, method, path, request id and key, filtered by key or status. It is the place to look when a script stops working: a key that has been answered403 since Tuesday shows as a row of them.
Keys aren’t pinned to a workspace. Switching your active workspace switches which pool a key spends from. See Team & workspaces.
