Developers
One key authenticates the CLI, the TypeScript and Python SDKs, and the raw HTTP API. Mint a key below, pick your tool, and everything you can do in this dashboard becomes scriptable.
Create an API key
Keys look like mk_..., are shown once, and never expire on their own. A key acts as you: full access by default. Need a narrower key for CI or a partner service? Scoped and project-limited keys live in Settings.
Revoking is instant and safe to do anytime: the key stops working, the agents it created keep running. To rotate, create the replacement first, switch your workload over, then revoke the old key. Keep keys in environment variables or a secrets manager, never in source control.
Pick your tool
Same key everywhere. The CLI is the fastest way to try things by hand; the SDKs are for wiring agents into your product; raw HTTP works from anything else.
# Install once npm i -g maritime-cli # Authenticate with your key export MARITIME_TOKEN=mk_... # Create an agent, talk to it, script everything maritime create researcher --template openclaw --json maritime chat researcher "summarize today's incidents" --json maritime list --json
Every command takes --json and returns structured output with real exit codes, so it drops straight into scripts, CI, and other agents. CLI reference
How billing works
A key acts on the same plan you see on Billing: agents it creates count against your plan's agent allowance, agents beyond that allowance bill at your plan's flat add-on price, prorated by day, and AI usage draws from your AI credits when agents use Maritime's built-in models.
If your plan has lapsed, the API returns 402, so check your plan is current before big provisioning runs. Rebilling your own customers? GET /api/v1/usage itemizes cost per agent and per end user.