Legal
Smol API Uptime Agreement
The availability we aim for on the Growth, Scale and Enterprise plans, how it is measured, and the credit you can claim if we miss it.
1. When this agreement starts
1.1This agreement starts on the first day of the calendar month after the service has completed 60 days in a row of measured production uptime, with the results published.
1.2We will announce the start date on this page and by email to customers on the plans it covers. Start date: [TO BE COMPLETED: start date, once the first 60 days have been measured].
1.3Months before the start date are not covered, and no credits are owed for them.
2. Who is covered
2.1This agreement applies to accounts on the Growth, Scale and Enterprise plans. It does not apply to pay as you go or to the Starter plan.
2.2Where an Enterprise contract sets its own uptime terms, those terms apply instead of this agreement.
2.3An account must be on a covered plan for the whole of the month concerned and must have no invoice overdue.
3. The target
3.1Our target is that the API is available for at least 99.9% of each calendar month (UTC). In a 30-day month that allows about 43 minutes of downtime.
3.2“The API” means the endpoints at api.smolmac.com that accept direct requests, accept and report on jobs, and serve results. It does not include the dashboard, the documentation or the website.
3.3The target is about whether the API accepts and answers requests. It is not a promise about how long a job takes to finish.
4. How uptime is measured
4.1An independent monitoring service outside our infrastructure sends a test request to the API once a minute from more than one location. The test is a direct request that compresses a small sample image, so it exercises the whole path, not only the front door.
4.2A minute counts as downtime when most of that minute’s tests fail. A test fails when it gets no answer within 30 seconds, or an answer with a server error (HTTP status 500 or above).
4.3Monthly uptime is the number of minutes in the month that were not downtime, divided by the number of minutes in the month, as a percentage. Minutes excluded under section 5 are left out of both numbers.
4.4The results are published at [TO BE COMPLETED: status page address and name of the monitoring service].
4.5If your own records show failures that the monitor missed, send us the request IDs (the Smol-Request-Id header) with your claim. Where our records confirm that the API was failing, we correct the month’s figure.
5. What does not count as downtime
5.1The following are excluded:
- planned maintenance announced on the status page at least 48 hours ahead, up to 4 hours in a month;
- requests refused for a reason on your side: an invalid request, an unsupported or oversized file, a rate or concurrency limit, the spend cap, an unpaid invoice or a suspended account;
- problems in your own systems or network, or in an address you asked us to fetch from or deliver to;
- requests made with test keys;
- features labelled beta or preview, and features switched on for individual accounts ahead of release;
- a suspension under the Terms of Service; and
- events outside our reasonable control, such as a failure of the wider internet or a natural disaster.
5.2An outage at our hosting provider is not excluded. If its failure makes the API unavailable, that counts as downtime.
6. Service credits
6.1If monthly uptime falls below the target, you may claim a credit worked out from that month’s plan fee:
| Monthly uptime | Credit, as a share of that month’s plan fee |
|---|---|
| Below 99.9%, but 99.0% or above | 10% |
| Below 99.0%, but 95.0% or above | 25% |
| Below 95.0% | 50% |
6.2The credit is based on the fixed monthly plan fee only. Charges for usage beyond the plan’s included amount are not part of the calculation.
6.3The most that can be credited for one month is 50% of that month’s plan fee.
6.4A credit is taken off a later invoice. It is not paid out in cash, and it lapses if the account closes before it is used.
7. How to claim
7.1Email [email protected] within 30 days after the end of the month concerned, with “Uptime claim” in the subject line.
7.2Include the email address on the account, the dates and times (UTC) of the downtime, and any request IDs you have.
7.3We check the claim against the published results and our own records and answer within 30 days. An approved credit appears on your next invoice.
8. Your only remedy
8.1Service credits under this agreement are your only remedy for the API being unavailable, as stated in clause 13.5 of the Terms of Service.
9. Changes to this agreement
9.1We may change this agreement as set out in section 16 of the Terms of Service. A change that lowers the target or the credits needs at least 30 days’ notice by email.