Skip to content
Docs / Authentication

Authentication

Every call to https://design.axm.lol/mcp needs an API key. A key ties calls to your workspace and shows usage by client and project.

Keys

  • Keys start with ast_live_ and belong to one workspace.
  • Create and rotate them under API keys on the dashboard.
  • A key is shown in full once, when created. We store a hash.

Sending a key

Over HTTP, send it as a bearer token. This request lists the tools and is a quick way to check a key:

Terminal
curl -s https://design.axm.lol/mcp \
  -H "Authorization: Bearer $ASTRON_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

With the mcp-remote bridge, pass the same header with --header; the bridge forwards it on every call.

Projects

Add X-Astron-Project to group usage by project on the dashboard. It is optional and free-form, for example ledgerly-web.

Terminal
claude mcp add --transport http astron https://design.axm.lol/mcp \
  --header "Authorization: Bearer $ASTRON_API_KEY" \
  --header "X-Astron-Project: ledgerly-web"

Rotation

Rotating issues a new key immediately. The old key keeps working for 24 hours so you can update every client without downtime, then stops with a 401.

Errors

  • 401 invalid_token: the key is missing, unknown, revoked, or past its 24-hour rotation window. The response carries a WWW-Authenticate header.
  • 405: the endpoint is stateless; send JSON-RPC with POST, not a GET event stream.
  • 429 rate_limited: see Rate limits.
Never commit a key. Reference it from the environment, as every example in these docs does.