Skip to content

Get an API key

An API key authenticates requests to the MaxoPerf Platform API — from CI pipelines, scripts, or an AI agent connected over MCP. You create it once from the console and paste it wherever a tool asks for a MaxoPerf credential.

  1. Open Settings → API keys (/settings/api-keys).
  2. Click New API key. Give it a name that says what it’s for — ci-nightly-run, claude-code-agent — so you can tell keys apart later.
  3. Pick an expiry. Choose 1 month, 1 year, or 10 years. Shorter expiries are safer for experimentation; long-lived keys suit stable CI pipelines.
  4. Copy the token immediately. It is shown once, in the form mpak_<keyId>_<secret>. If you navigate away before copying it, you’ll need to revoke the key and create a new one — MaxoPerf never re-displays the secret.

”Read-only” isn’t a setting — it’s a habit

Section titled “”Read-only” isn’t a setting — it’s a habit”

MaxoPerf doesn’t yet offer a read-only key type. If an AI agent only needs to inspect dashboards, KPIs, or run history, get the same safety by:

  • Instructing the agent (in its system prompt or skill config) to avoid create/run/delete tool calls.
  • Reviewing the agent’s tool-call log before approving anything destructive (delete run, cancel test, revoke key).
  • Rotating the key on a schedule and watching Last used on the API keys page for calls you didn’t expect.

Pass the key as a bearer token:

Terminal window
curl -H "Authorization: Bearer mpak_your_api_key_here" \
https://api.maxoperf.com/v1/tests

AI tools connecting over MCP use the same header — see Connect AI tools for per-client setup, or Install the MaxoPerf skill for the fastest on-ramp.

Open Settings → API keys, find the key by name, and click Revoke. Revocation is immediate — any tool still using that token starts getting 401 Unauthorized on its next call.