API keys

Format, storage and lifecycle.

Format: messy_live_ or messy_test_ followed by 44 base62 characters.
Shown once at creation. Only a SHA-256 hash and the last four characters are stored.
One account, one key model: every key can call every capability. The number of keys depends on your plan.
Rate limits and quotas apply per organization, so extra keys don't multiply your budget.

Scopes

Endpoint scopes (e.g. messyapi:normalize) are documented as a forward model but are not currently enforced. Treat every key as full-access.

Try it

curl -X POST https://messyapi.com/api/v1/repair \
  -H "Authorization: Bearer $MESSYAPI_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "records": [
    {
      "Company Name": "ACME, INC.",
      "Email": " JOHN@ACME.COM "
    }
  ]
}'

Open in playground →Starter project →Use with Claude / Cursor →