API Key Management
Create keys in API Keys for the selected regional account. Save the full mks_ token securely when it is shown once. The token's prefix is followed by 48 ASCII letters/digits. A later masked preview is an identifier and cannot make requests.
Use an environment variable or secret manager for MAKAS_API_KEY. Keep provider credentials separately. If the full key is lost, create a replacement and revoke the old key when appropriate; there is no secret recovery from its preview. Rotate by deploying the replacement, verifying traffic and then revoking the previous key. Expired/revoked keys fail authentication.
Per-key routing controls and spending caps require Scale+ in planned paid tiers, and are included in Founding. This does not remove account quotas.
First-launch billing is off: new accounts receive the free Founding plan without a card. Paid tier references describe planned billing-on behavior; plan reservations do not enable paid billing.
Founding includes 5,000,000 requests/month, 200 requests/minute, 3,000,000,000 tokens/month, 10 API keys, 5 team members and 10 custom routing rules; request logs retain 30 days and analytics 90 days. It includes all currently live feature gates except semantic caching. Customer-specific quota overrides can change effective limits.
Exceeding a plan limit returns 403 with type: urn:makas:error:limit-exceeded and limitType, limit and current.
See authentication and complete examples.