Request an API key for a site you are running on (challenge-response).
This starts a two-step verification flow:
1. A claim token is written to your container at ~/.borealhost/.claim_token
(mode 600, owner admin — only readable if you're on the container)
2. Read that file and call claim_api_key(token) within 1 hour
This proves you have access to the container without storing any secrets
on disk permanently. The claim token is single-use and ephemeral.
No authentication needed — the proof is reading the file from the container.
Args:
site_slug: The site identifier (your BorealHost site slug)
Returns:
{"status": "pending", "site_slug": "my-site",
"expires_in_seconds": 3600, "claim_path": "~/.borealhost/.claim_token",
"instructions": "Read the claim token and call claim_api_key()..."}
Errors:
VALIDATION_ERROR: Unknown site slug or no active subscription
RATE_LIMITED: Too many pending claim tokens
Connector