How it works
Your request,
step by step.
Makas sits between your application and your provider. Here is what happens to each request, in order.
Request flow
From your serverto the provider.
Your request arrives
Your server sends a provider-native request to a regional Makas mirror, with your Makas API key and your provider key.
Prompt analysis
Each request is classified by task type, such as code, creative or analytical, and by complexity: simple, medium or complex. A small embedding model running inside Makas classifies by default, so classification sends the prompt nowhere else. Keyword matching is the fallback.
Routing decision
Your rules are evaluated first, then the defaults, each in priority order. Rules that can raise cost are off by default, and routing stays with the provider you called.
Forwarded to your provider
Makas forwards the request with your provider key in the provider's native header and records usage metadata.
Resilience
Each provider has its own circuit breaker, so an outage fails fast instead of hanging. Non-streaming requests retry provider errors with backoff.
Both prices, logged
Each decision is logged with the model, the rule and both prices.
What is stored
What we keep,and what we don't.
Your prompts
Makas does not store your prompts or responses. Request logs keep usage metadata such as the model, tokens and cost, never the text.
Your provider
Requests still leave Makas for the provider you selected, and that provider's policies and your agreement with it apply.
What is recorded
Each decision is logged with the model, the rule and both prices.
Semantic caching is not offered yet. Before it is switched on, this page and the Privacy Policy will say what it stores.
Your keys
Your keyspass through.
Two keys on each request
Your Makas API key goes in the Makas-Api-Key header and identifies you to Makas. Your provider key goes in the provider's native header. Makas removes its own key before the request goes upstream.
Your provider key is not stored
Your provider key comes with each request and is used in memory to call the provider. We don't store it. Makas API keys are stored hashed. Sessions use JWTs signed with RS256.
Usage stays on your account
Provider usage remains on your own provider account.
Regions
Separate regions,separate accounts.
Europe: live
Your Makas account is hosted in Europe. LLM providers and operational services may process data elsewhere.
United States: coming soon
Not open yet. Accounts there will be independent of your Europe account.
Independent accounts
Regions use independent accounts and credentials. Each region has its own account, and traffic does not fail over between regions.
Questions
Before youchange that URL.
Do I keep using my own provider keys?
Yes. Makas uses your provider credentials to forward requests. In the current pass-through mode, send the provider key with each request alongside your Makas API key. Provider usage remains on your own provider account.
Does routing switch between providers?
Routing stays within the provider your request arrived on. An OpenAI request stays with OpenAI, an Anthropic request stays with Anthropic, and a Google request stays with Google.
Does every request get routed?
No. Routing stays within the provider your request arrived on, and the model changes only when a rule fits. Request capabilities, request shape and conversation continuity can prevent a change, and a low-confidence classification can keep the model you requested. A successful request can come back with Makas-Was-Routed: false and zero savings.
Can I see what happened to a request?
Yes. Each routing decision is logged with the model, the rule and both prices, and you can compare the model you requested with the one used in your request logs. Buffered responses can also carry Makas-Model-Requested and Makas-Model-Used headers when a routing decision exists.
What happens to my prompts?
Makas does not store your prompts or responses. Request logs keep usage metadata such as the model, tokens and cost, never the text. Semantic caching is not offered yet. Before it is switched on, this page and the Privacy Policy will say what it stores.
Which regions are available?
Europe is live and the United States is coming soon. Regions use independent accounts and credentials, so each region has its own account, and traffic does not fail over between regions.