Aegis
Aegis

API keys

API keys let you submit sequences from scripts, notebooks, or CI without going through the browser sign-in flow. They're scoped to your user and count against your rate limits.

Account page
The Account page — API keys, MCP setup, and account deletion live here.

Create a key

  1. Go to Your account.
  2. In the API keys card, click Create key and give it a descriptive label (“laptop notebook”, “CI pipeline”).
  3. Copy the key immediately — it's displayed once and then stored as a hash. If you lose it, revoke and create a new one.
Key hygiene
Treat the key like a password. Don't commit it; don't share it. Inactive keys are auto-deactivated after API_KEY_INACTIVE_TTL_DAYS (default 90 days).

Using a key

Pass the key as the X-API-Key header. Minimal curl example:

curl -X POST https://radicalaegis.com/api/v1/analyze \
  -H "X-API-Key: $AEGIS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "service": "pipeline",
    "sequences": [
      { "id": "sample-1", "sequence": "ATCG..." }
    ]
  }'

The same endpoint accepts ?async=true to return a job id immediately; poll GET /api/v1/jobs/{id} or open the SSE stream for progress.

Revoking a key

On Your account, click Revokenext to the key. It stops working immediately. List and revoke via API with GET /auth/api-keys and DELETE /auth/api-keys/{id}.

Rate limits with keys

API-key traffic is limited per user: 100 requests/min, 3 job-submissions/min, 3 concurrent jobs, 20 sequences and 20M nucleotides per job. Admins get a 5× multiplier; privileged email domains are auto-granted higher limits. When you hit a limit the API returns 429 with a Retry-Afterheader — back off and retry.