Akada / Trust

Security

How Akada handles connections, account access and API credentials.

Encrypted connection

Use https://aiakada.com for the public website, sign-in and API calls. Model traffic goes through the gateway to the upstream service selected by its routing configuration.

Identity and permissions

The account backend verifies sign-in and enforces access to account records and administrative actions. You can manage your password and any available two-factor settings from your account profile.

Open account security

API key controls

Create a separate key for each tool or deployment. Where available, set a quota and expiration. Disable exposed keys in the workspace and issue replacements to the affected tools.

Manage keys

Report an issue

Contact the administrator who provided your account. Include the affected path, approximate time and request ID when available. Keep passwords, full API keys and sensitive payloads out of the report.

Check service status