Audit-ready history
Trace each request through its supply group, model, key and result.
- Per-request records
- Exportable logs
Connect your tools, manage API keys, and follow your model usage in one calm workspace. Akada brings your everyday AI work together.
Your keysYour usageOne connection
Accounts
Open your Akada workspace to manage keys, check your balance and follow your model usage. Find subscriptions and order history on the accounts page.
Explore accountsAkada workspace
API keys, model access and USD usage
Order history
Find the lookup for your purchase
Anthropic’s standard API list prices. Your Akada key’s group determines access and billing.
USD per 1M tokens
claude-opus-5-5
For complex coding, long-running agents and multi-step analysis.
claude-sonnet-5-5
A balance of speed and reasoning for everyday coding and analysis.
claude-haiku-5-5
For fast, high-volume work such as classification and extraction.
A familiar API connection, with a workspace that keeps the important details close.

Keep each key attached to its assigned group and supported models.
Use Anthropic Messages or OpenAI-compatible endpoints with the appropriate key and model.
See usage and request outcomes without keeping a terminal open.
Keep tools and environments separate with named API keys.
Follow tokens, requests and USD usage from your workspace.
Customers, suppliers and operators work within their own permissions.
Create a key, choose its supply group, then watch requests, usage and billing in one place without touching application code.
API keys
| Name | Group | Status |
|---|---|---|
| Production keysk-akada-•••• | Official | active |
| Claude Code keysk-akada-•••• | Subscription | active |
| CI keysk-akada-•••• | Bedrock | active |
Four clear views of your requests, access, limits and ownership.
Trace each request through its supply group, model, key and result.
Keep model and supply-group access in one place. Your app uses the corresponding key.
Account and group limits remain enforced by the gateway. Follow the returned error and retry guidance.
Separate keys by team, service or environment to keep usage and costs attributable.
The questions teams ask before trusting a gateway with production traffic, long term.
Still deciding? Open your workspace
Existing platform accounts use the same credentials. Open the workspace and sign in. Your account permissions determine the pages, groups and models available to you.
Open API keys in your workspace. Create a key for an available group, then copy it into your tool. An API key is a secret; only share it with tools you trust.
Your assigned group, balance, permissions and upstream availability determine what can be used. The authenticated workspace shows your actual configuration and recorded USD usage. Public examples do not guarantee model access or a particular rate.
Yes, use the connection guide and the models your key can access. The base URL is https://aiakada.com for Anthropic Messages, or https://aiakada.com/v1 for OpenAI-compatible SDKs.
No. Availability depends on your account, quota and the upstream provider. Authentication, quota, unsupported models and provider outages can reject requests. Review the returned error and your workspace records before retrying.
Use the billing options enabled for your account, or contact the administrator who supplied it. No payment is confirmed by a browser redirect alone.
Create a key, pick a supply group, and set your base URL to aiakada.com. Review your recorded requests and usage in the console.
export ANTHROPIC_BASE_URL="https://aiakada.com"export ANTHROPIC_API_KEY="sk-YOUR-AKADA-KEY"