Welcome to Makas
Makas is a provider-compatible proxy for routing and cost visibility. Connect your server-side client, send a request, and inspect what happened in Request Logs. Savings depend on request shape, rules and model pricing; no request has a guaranteed saving.
Send your first request
-
Choose your region and provider. Select EU or US in the docs region selector, then open a complete quick start:
Accounts and keys are separate in each region. The selector updates example endpoints and Dashboard links; static examples default to EU.
-
Create an account and a Makas key. Sign up at Register and confirm the verification email; unverified accounts cannot create keys or send requests. Then open API Keys in your chosen region. Save the full token when it is shown, and have your provider's own key ready.
-
Send a request. Choose Python, TypeScript or cURL in your provider's quick start. Prepare the runtime and credentials, then copy and run the complete example on your server or local development machine.
-
Inspect Request Logs. Open Request Logs in the same region to check the outcome, model and available cost metadata.
For help with keys and headers, see Authentication. For request errors, start with quick-start troubleshooting. How it works explains the request path.
Launch availability and limits
First-launch billing is off: new accounts receive the free Founding Customer plan without a card. Paid tier references describe planned billing-on behavior; plan reservations do not enable paid billing.
Founding Customer accounts include:
| Allowance | Limit |
|---|---|
| Requests per month | 5,000,000 |
| Requests per minute | 200 |
| Tokens per month | 3,000,000,000 |
| API keys | 10 |
| Team members | 5 |
| Custom routing rules | 10 |
| Request log retention | 30 days |
| Analytics retention | 90 days |
This includes all currently live feature gates except semantic caching. Customer-specific quota overrides can change effective limits. Semantic caching and stored provider keys are disabled at first launch.