Identity
We ask each model who it is, under different system prompts and customer personas. A model that names another product, or drops the instructions it was given, fails.
Lower prices.
Verified models.
Zurelay buys AI capacity from independent sellers and tests it before it serves a single request, then keeps testing every day. Here’s where the savings come from, how we check that each model is the one it claims to be, and how to sell through Zurelay.
Where the savings come from
AI capacity is bought in bulk. Not all of it gets used.
List prices are what one developer pays for one request. Capacity bought ahead costs far less, and some of it would otherwise go to waste.
- 01
Capacity is bought ahead
Companies and AI platforms buy model capacity in advance: prepaid credits, committed-spend contracts, volume tiers and plan allowances. Bought that way, each token costs far less than list price.
- 02
Not all of it gets used
Usage rarely matches the forecast. Capacity that isn’t used by the end of its term is simply lost, so its holders would rather sell it below list price than let it lapse.
- 03
We match it to your requests
Zurelay pools several sellers for each model, tests every route, and sends each request to capacity that is available, verified and well priced. You pay a fraction of the list price for the model you named.
Because requests are served by independent infrastructure providers rather than by the model makers themselves, a model maker’s own terms for its customers don’t apply to them. Our Terms (sections 3.3 and 3.4) explain how requests are served and what our checks cover.
How we verify
Every route is tested. Before it serves anyone, and every day after.
A model name on a price list proves nothing. These checks are how we know a route serves the model it says it does, the way it should.
Knowledge
Each model generation knows the world up to its own training date. Questions about dated events with known answers catch an older or cheaper model sold under a newer name.
Reasoning
Problems with one exact answer catch a smaller model swapped in for a larger one, even when its writing sounds the same.
Response details
We compare the model name and token counts a route reports with what we sent. A mismatch points to a different model or extra hidden instructions, and you’re never billed for tokens you didn’t send.
Image output
We ask for specific sizes and aspect ratios and measure what comes back. A route that returns a smaller image, or another model’s output, fails.
Tools and streaming
Tool calls in OpenAI and Anthropic formats, and streaming, have to work as the model maker documents them.
After a route goes live
Passing once isn’t enough. Sellers can change what runs behind them at any time, so the checks never stop.
What these checks cover
They test quality and reliability: that you get the model you asked for, working as it should. They aren’t audits of a seller’s security or data handling. We don’t publish the exact tests, so they can’t be gamed.
- Every 10 minutesEvery chat model gets a test request of our own, on top of watching live traffic. A route that errors or stalls is dropped for that request and retried elsewhere.
- Every dayKnowledge and identity checks run again, because a seller can change what runs behind it overnight.
- On every requestAn error page sent as an answer, or an image at the wrong size, counts as a failed attempt: the request moves to another route and you aren’t billed for it.
- When a route failsIt’s taken out of rotation until it passes every check again, and the model’s other routes keep serving it.
Building on Zurelay? The verification docs cover the same checks from the API’s side, and the status page shows every model’s health right now.
Sell through Zurelay
Have capacity to spare? Put it to work.
We work with companies and individuals who serve AI models reliably and below list price. This is what we look for, and how it works.
The model, as named
No substitutes, no quiet downgrades, and no older snapshot under a newer name.
Requests passed through as sent
No added instructions that change answers, and nothing inserted into outputs.
Prompts kept private
No storing, reviewing or training on requests beyond what serving them needs.
The right to resell
Capacity you’re allowed to resell, from accounts and agreements you control.
Steady capacity
Concurrency that matches what you offer, and clear errors when you’re at your limit.
Prices below list
A price well under the official list price, held steady or changed with notice.
- 1
Apply
Tell us what you serve, how much traffic you can take and roughly what it costs. It takes about three minutes, and no keys.
- 2
Review
A person on our team reads every application and replies by email, usually within three business days.
- 3
Test
We run every check on this page against your service. Nothing reaches customers until it passes.
- 4
Go live
We agree prices and payment terms, add you to routing, and keep checking every day.
Apply
Apply to sell.
It takes about three minutes. A person reads every application, and we reply by email.
- No API keys or passwords. If you’re a fit, we’ll explain how to set up a test.
- A reply by email, usually within three business days.
- The same checks for every seller, before any customer traffic.
- Questions first? Ask our team.
Do you need my API keys to apply?
No. The application never asks for keys or passwords, so please don’t send them. If your service is a fit, we’ll explain how to set up a test.
Which models are you looking for?
Any model in our catalog, and models we don’t carry yet. More sellers for a model means better uptime for customers, so we welcome sellers for models we already serve too.
Can individuals apply, or only companies?
Both. We judge the service, not the size of the business behind it: the model has to be genuine, the capacity steady and the price below list.
How are sellers paid?
We agree prices, currency and payment terms with each seller before any traffic starts.
Can customers choose which seller serves them?
No. Customers choose a model and Zurelay chooses the route. We don’t name sellers to customers, and we don’t send sellers our customers’ names, email addresses or billing details.
Is my request always served by the model I asked for?
Every route is tested for that before it serves customers and every day after, and a route that fails is taken out of rotation. Our Terms describe what these checks cover.