Any admin can create an API key from Settings. Here is the flow, what the permissions mean, and where MCP differs.
If your team is not on McLeod, Tai or Turvo, you do not have to wait on us to connect. Any admin on your Cargado account can create an API key themselves, today, with no ticket and no call.
Keys look like cgk_live_... for production and cgk_test_... for testing. Send it as an api-key header, or as a bearer token.
Put the key in your platform's own secret store, not in a spreadsheet, a chat message or an email. If you think one has leaked, rotate it: rotation issues a new key and leaves the old one working for seven days so you can cut over without downtime. You can also revoke a key outright.
The endpoints themselves are documented at docs.cargado.com.
Cargado has an MCP server, which is how an AI assistant such as Claude talks to the marketplace. It does not use these API keys. It authenticates as you, through a normal Cargado sign-in, which means it can only ever see what your own account can see.
If you want to set that up, email success@cargado.com and we will walk you through it.
If you have seen a Cargado CLI mentioned somewhere, it does not exist. The two ways in are the REST API with a key, and MCP with a sign-in.