reflexer · reflexer.ai
You are paying frontier prices
for tasks that aren’t frontier work.
1 / 12
We are all paying way too much in tokens right now.
Look at your last month of traffic.
The same jobs come back again and again — greetings, confirmations, a field pulled out of a message, a decision from a short list.
Every one of them was paid at frontier prices, as if it were the first time.
2 / 12
Repetition should be cheaper.
Humans get faster at what they repeat. After a hundred times it costs almost nothing.
A frontier model does not work that way. Providers discount the repeated part of the prompt, but the answer itself is made from zero on every call — the first time and the thousandth.
3 / 12
How repetition looks in real traffic
Your assistant says hello by calling a frontier model and having it write the sentence out, start to finish, in every new chat.
And where it applies a rule, it composes a paragraph explaining the outcome, in new words each time, for a decision the policy had already made.
4 / 12
reflexer answers the routine work.
reflexer sits in front of the frontier provider you already call.
The routine requests are answered by your model, which we build from your own traffic: the same answer your provider would have given, faster, at half of the price they would have charged.
When a request needs frontier intelligence, it goes to your frontier provider, on your key. We charge only for the requests we answer.
5 / 12
No work lands on your team.
reflexer improves while your product runs, on your traffic, without anyone on your side doing anything about it.
Change a prompt whenever you like. Those requests go back to your frontier provider, and reflexer learns the new answers.
No data preparation, no training schedule, no review of your model on your side.
6 / 12
One line, and everything else stays as it is.
reflexer speaks the same API as the major providers, in the SDK and at the endpoint. You swap one line in your code.
Your key stays your key. Your rates, your credits and your terms stay as they are.
Your model is built from your traffic, used for you only, and destroyed when you leave.
Every response says which side answered it.
7 / 12
Your quality is never what is at stake.
We answer only when we know our answer matches the one your provider would have given.
Every request we send on comes back with the frontier answer, and we compare it with the answer we would have given.
When there is any risk we do not match, we abstain and the request goes to your provider.
So the thing that moves is how much of your traffic we cover — our bill, not your product.
8 / 12
How reflexer would look in real traffic
9 / 12
A circuit breaker with fallback to your frontier provider.
If anything on our side is degraded, a circuit breaker sends your traffic straight to your frontier provider. Your product keeps working and your users see nothing.
And if at any time you want out, you just stop calling us. No migration, no rewrite, nothing to unwind.
We want you to stay because the bill is lower, not because leaving is hard.
10 / 12
Half price on what we answer. Nothing on the rest.
For every request reflexer answers: half of what your frontier provider would have charged for it.
For every request we pass to your provider: nothing.
Every response carries what it cost, so the invoice can be checked request by request.
11 / 12
Closed beta, starting Q4 2026.
Not live yet. We start with a small group of companies in Q4 2026.
Want in? Tell us what you run at hello@reflexer.ai.
12 / 12
Team: one founder.
I am Rafael Carrascosa. At Mercado Libre I was Director and then Senior Principal of machine learning, with over a hundred people in my org.
Before that I co-founded a startup, meshh, and was part of the team that sold Machinalis to Mercado Libre.
reflexer is all I do, and then some. In the beta you talk to me directly, the person who builds the models.
Know a team with a big token bill? Send them my way.
LinkedIn · hello@reflexer.ai