API monitoring pricing, from EUR 3 a month
Pay for the checks you run, not the endpoints you own. Free up to 5,000 checks a month, then EUR 3. Fifteen days of Pro, no credit card.
No credit card required
After your trial
Choose the plan that fits your needs, or continue with limited free access.
- Status monitoring
- Email alerts
- MCP AI Integration
- Everything in Free
- MCP AI Integration
- Priority support
Every plan, side by side
| Checks per month | Price | Roughly |
|---|---|---|
| 5,000 | Free | 1 endpoint every 9 min |
| 10,000 | EUR 3 / month | 1 endpoint every 4 min |
| 20,000 | EUR 5 / month | 1 endpoint every 2 min |
| 40,000 | EUR 9 / month | 1 endpoint every 1 min |
| 80,000 | EUR 15 / month | 2 endpoints every minute |
| 160,000 | EUR 25 / month | 4 endpoints every minute |
| 320,000 | EUR 39 / month | 7 endpoints every minute |
| 640,000 | EUR 59 / month | 15 endpoints every minute |
| 1,280,000 | EUR 89 / month | 30 endpoints every minute |
| 2,560,000 | EUR 149 / month | 59 endpoints every minute |
| 5,120,000 | EUR 229 / month | 119 endpoints every minute |
| 10,240,000 | EUR 349 / month | 237 endpoints every minute |
All paid plans include the same features. The only thing that changes between them is the number of checks. No per-seat fee, no annual commitment, no charge for adding an endpoint.
What you are paying for
A check is one request to one endpoint. Most monitoring tools bill per monitor, which treats an endpoint polled once an hour the same as one polled every minute, sixty times the work for the same price. The practical effect is that people stop splitting a service into separate checks, because each split costs money, and end up watching a single URL that stands in for eight.
Billing per check removes that trade-off. Add the rarely polled endpoint. It costs close to nothing.
What a check actually verifies
Status code, response time, and the JSON body itself against a schema you describe once. That last part is the reason the free tier is worth using rather than a plain ping: an endpoint answering 200 with a null field, an empty array or a price that silently became a string is reported as a failure, not a success.
Alerts go out by email, webhook, SMS, WhatsApp, iMessage or RCS, and carry the response that failed, so you can tell a transient blip from a real regression without opening anything.
Where the free tier stops
5,000 checks a month, status monitoring and email alerts, with no card and no expiry. It covers a side project honestly. What it does not include is the MCP server, so setting up and querying monitoring from Claude Code or Cursor starts at EUR 3 a month. See the MCP integration, or how this compares to other monitoring tools.
Questions about pricing
How much does Safeship cost?
Free up to 5,000 checks a month, then EUR 3 for 10,000 checks, EUR 15 for 80,000 and EUR 349 for 10.24 million. You pay for the checks performed, not for the number of endpoints you watch.
What counts as a check?
One request to one endpoint. An endpoint polled every five minutes uses about 8,640 checks a month. The same endpoint polled hourly uses 720. Ten endpoints polled hourly cost less than one endpoint polled every minute, which is the point of billing this way.
Is there a free plan?
Yes, 5,000 checks a month with no card and no expiry. That covers one endpoint every five minutes, or five endpoints every hour. Status monitoring and email alerts are included. The MCP server and the AI editor integration are not.
Do I need a credit card to start?
No. The 15 day trial opens every Pro feature, including 80,000 checks and the MCP integration, without any payment details.
What happens after the 15 day trial?
Nothing is charged automatically. You either subscribe to keep Pro features, or you fall back to the free 5,000 checks a month. No card was taken, so there is nothing to cancel.
Can I change plan later?
Yes, up or down at any time from billing settings. Changes take effect on the next cycle, there is no annual commitment and no minimum term.
Why per check instead of per monitor?
Because per monitor pricing charges you for the number of things you watch rather than the work done watching them, which pushes people to monitor one URL standing in for eight. Billing per check means adding a rarely polled endpoint costs close to nothing.