Get started

Get an API key

An API key identifies your account on every request. This page covers creating one, keeping it safe, and replacing it.

Create a key

  1. Open the dashboard

    Sign in and go to your dashboard.

  2. Choose Create API key

    The key appears once. Copy it before you close the banner. Keys look like taxmcp_ followed by 40 hexadecimal characters. Only a hash is stored, so a lost key cannot be shown again; create a new one instead.

  3. Send it on every request

    Use the standard bearer header over HTTPS:

    Authorization: Bearer $TAX_MCP_API_KEY

Keep it safe

Treat it like a password

  • Store it in an environment variable or a secret manager. Never commit it to source control.
  • Call the API from your server. Never ship the key in browser or mobile code.
  • Never put it in a URL, a log line, or a screenshot.
  • Never paste it into feedback or a support email. Support will never ask for it; describe the request instead.

Use a separate key for each integration, for example one for your production backend and one for an assistant you connect yourself (see Use from Claude or ChatGPT). You can then revoke one without touching the others. All of an account's keys share its monthly quota, so a leaked key can use up that quota until you revoke it.

How many keys you can have

PlanAPI keysCalls per month (shared by all keys)
free1250
developer22,500
startup520,000
scale10150,000

Enterprise plans are contracted; see Pricing.

Rotate a key

  1. Create a new key in the dashboard.
  2. Deploy it to every place that uses the old key.
  3. Revoke the old key. Requests that still use it start receiving 401 at once.

Revoke a key

Choose Revoke next to the key in the dashboard. Revocation is immediate and permanent. Revoke at once if a key may have been exposed, then create a replacement.

When a key is rejected

Authentication failures are never billed. The body tells you which case you hit:

401 — missing, unknown, or revoked key
{
  "error": "unauthorized",
  "billed": false,
  "retry_safe": false,
  "next_action": "check_credentials",
  "reason": "unauthorized"
}
403 — the key is valid but the account is suspended
{
  "error": "account_suspended",
  "billed": false,
  "retry_safe": false,
  "next_action": "check_credentials",
  "reason": "account_suspended"
}

To check a key without using quota, send a GET to https://tax-mcp.com/api/mcp/tax-compute/federal with the header. For a 403, email support@tax-mcp.com.

See also: Requests & authentication.