Get an API key

Keys are admin-minted today. Self-serve signup is future work.

Request a key

Contact the operator to request a key. Include the metadata an operator needs to mint one:

• label — a human-readable name for the key (e.g. acme-prod).
• owner contact — an email / channel to reach the key owner.
• tier — free or partner (selects the default rate limit; an explicit per-key limit can override it).

How an operator mints it

Two equivalent paths (issue #12, M2-T0):

Admin REST API

curl -X POST \
  -H "x-admin-token: $MEA_ADMIN_TOKEN" \
  -H "content-type: application/json" \
  -d '{"label":"acme-prod","owner":"ops@acme.example","tier":"partner"}' \
  https://mina-explorer-api.minaprotocol.com/admin/v1/keys

The admin surface (/admin/v1/keys) is mounted only when MEA_ADMIN_TOKEN is configured, and is guarded by the x-admin-token header (never the public x-api-key).

CLI

python -m app.keys mint --label acme-prod \
  --owner ops@acme.example --tier partner

Using the key

Send it as the x-api-key header on every request:

curl -H "x-api-key: $YOUR_KEY" \
  https://mina-explorer-api.minaprotocol.com/mina-mainnet/v1/info

Self-serve signup

Future work. A self-serve signup portal is planned but not part of launch. Until then, all keys are admin-minted via the flow above.

← Migration guide · Compatibility matrix