# otp-watch

> Synthetic monitoring for SMS/email verification delivery. Rent a real phone number or disposable email, trigger your own OTP send to it, then poll for whether — and how fast — the code actually arrives.

Most uptime monitors confirm your API responded 200. None of them confirm the SMS or email your OTP provider promised to send actually showed up. otp-watch does just that one thing, for both channels.

## How it works

- One-off check: `POST /checks` rents a fresh target (phone number or email) and returns it immediately. Trigger your own verification send to it, then poll `GET /checks/:id` until `received` (with latency in ms) or `timed_out`.
- Email checks are free and unlimited. One-off SMS checks include 3 free per key (each one rents a real number), after which `POST /checks` returns `402` — check what's left with `GET /usage`.
- Monitor (€29/month, for repeated automated checks): `POST /monitors/checkout` rents one number for 30 days and reuses it across unlimited checks — the only sane way to run frequent SMS checks from your own cron/CI.
- No signup beyond an email for an API key: `POST /keys`.

## Docs

- [README / full API reference](https://github.com/flovoice53-tech/otp-watch): quickstart curl examples, all endpoints, monitor lifecycle.
- [FAQ](https://otpwatch.flo-voice1.com/faq): pricing, timeouts, CI usage, limits, what the SMS number is.
- [Monitoring OTP delivery](https://otpwatch.flo-voice1.com/guides/monitoring-otp-delivery)
- [Testing OTP integration without burning SMS credits](https://otpwatch.flo-voice1.com/guides/testing-otp-integration-without-burning-sms-credits)

## Related

- [sms-florin](https://flo-voice1.com/llms.txt): the phone-number rental service otp-watch's SMS channel runs on.