Corent is one API in front of many model suppliers. Our job is to notice a supplier failing before you do and route around it. This page says exactly what is monitored, how fast a person is paged, what happens to your money when a render fails, and how to get a refund on a result that finished badly. Updated September 12, 2026.

Every supplier, every minute

Each model supplier is probed once a minute, and every real generation feeds the same signal. Three failures in a row take a supplier out of routing for five minutes; requests reroute to the next one without you doing anything.

Sign-in, every 45 seconds

Login and sign-up are probed separately from the rest of the site, because they can break while everything else works. Two misses in a row, about 90 seconds, page a person. Recovery pages them again.

A real render, every week

Once a week the pipeline renders a test image in each orientation and measures the pixels that come back. A wrong shape pages a person, because a review cannot catch a supplier quietly ignoring a setting.

Live status, not a promised percentage

The status page is the API reporting on itself, refreshed every 30 seconds. Each tier reads operational, degraded or down. Degraded means the tier still completes requests but fewer than 90 percent of recent jobs across its suppliers finished, so expect slower or fewer models. Down means no supplier for that tier is answering. We do not publish an uptime percentage, because we do not yet keep the history that would make one honest. When we do, it will appear there first.

Failed renders are never billed

Your balance is prepaid. When a request arrives, the estimated charge is held, not taken. It is taken only when a result is delivered. If every supplier fails, the hold is released, the job is marked failed, and its receipt reads billed: false, cost 0. That includes the attempts we made on your behalf while rerouting: a failed try costs us, never you.

Quality refund

A render can finish and still be wrong: the wrong shape, a corrupt file, a setting silently dropped that the response did not disclose. Send the request id from the response to support@corent.tech within 30 days. A person reads the receipt and the routing log, and if the result was not what you asked for, the charge is credited back to your balance. Taste is not a defect: a correct render you simply do not like is not refunded, and we will say so plainly.

When you write in

Support answers within one business day. Security reports go to security@corent.tech and are looked at the day they arrive. An outage does not need a ticket to reach us: the monitors above page a person directly, and the status page shows what they see.

What this page is

This is a service commitment: what we monitor and what we do when it fails. It is not a contract. It becomes one only when a signed version, countersigned by Corent, sits beside your agreement. Until then the terms govern, and they say the same thing this page does: you never pay for a failed generation, and every charge is auditable on its receipt.

What we watch, and what we owe you when it breaks.