Skip to main content

​
Authentication Method

The BRIK-64 API uses Bearer token authentication. Include your API key in the Authorization header: 
Authorization: Bearer brik_live_xxxxxxxxxxxxxxxxxxxx

​
API Key Format

API keys follow the format brik_live_ followed by a random alphanumeric string: 
brik_live_a1b2c3d4e5f6g7h8i9j0k1l2m3n4
Keep your API keys secret. Do not commit them to version control or expose them in client-side code.

​
Register for an API Key

curl -X POST https://registry.brik64.dev/v1/auth/register \
  -H "Content-Type: application/json" \
  -d '{
    "email": "you@example.com",
    "name": "Your Name"
  }'
Response: 
{
  "api_key": "brik_live_a1b2c3d4e5f6g7h8i9j0k1l2m3n4",
  "message": "API key created. Store it securely — it cannot be retrieved later."
}

​
Managing Keys

​
List your keys

curl https://registry.brik64.dev/v1/auth/keys \
  -H "Authorization: Bearer brik_live_xxx"

​
Revoke a key

curl -X DELETE https://registry.brik64.dev/v1/auth/keys/<key-id> \
  -H "Authorization: Bearer brik_live_xxx"

​
Rotate a key

curl -X POST https://registry.brik64.dev/v1/auth/keys/rotate \
  -H "Authorization: Bearer brik_live_xxx"
Returns a new key and invalidates the current one.

​
Public Endpoints

The following endpoints do not require authentication:
  • GET /v1/health
  • GET /v1/catalog
  • GET /v1/catalog/:mc_code
  • GET /v1/circuits (public circuits only)

​
Using with the CLI

# Store your key for CLI use
brikc auth login --key brik_live_xxx

# Or use environment variable
export BRIK64_API_KEY=brik_live_xxx