TeeScoutBot

A program that reads public golf tee sheets. This page exists because our requests name it, and a contact address nobody can reach is not a contact address.

If you operate a golf course or a booking platform and you want us to stop reading your tee sheet, skip to removal. We will do it within 24 hours and we will not ask you why.

What it does

TeeScoutBot fetches the same publicly visible tee-time availability pages a golfer sees in a browser, notices when a tee time appears or disappears, and tells the golfer who asked to be told. That is the entire function.

It behaves like one careful person refreshing a page, not like a crawler. It reads one course's availability for one date at a time, on a fixed schedule, from one address.

How often, exactly

These are hard limits in the code, not guidelines. The floor is absolute: no configuration, no customer, and no amount of demand lowers it.

Limit	Value
Minimum interval between reads of the same course and date	60 seconds
Typical interval in practice	300–1800 s
Requests per course per day (2026-08-05)	~2,900
Maximum request rate, per booking platform	1–2 req/s
Actual measured rate, all platforms combined (2026-08-05)	0.9 req/s
Courses read	41
Concurrent connections per host	2

That per-course figure is the honest one and it is higher than it first looks, because we track roughly a week of dates at each course and each date is read separately. It works out at about one request per course every 30 seconds, spread across seven pages — well under what a single human hitting refresh on one page would generate.

Adding courses does not raise our traffic. When the schedule would exceed a platform's cap, every interval is stretched proportionally instead — so growth makes us slower, not louder.

If you refuse us, we stop

Any 401, 403 or 429 from a course permanently quarantines it. We do not retry harder, rotate addresses, change our user-agent, or come back later to see if you have changed your mind. A refusal is final until a human at our end reviews it.

We read anonymously. No account, no login, no session is carried between courses, and no cookie set by one course is ever sent to another.

What it never does

• It never books a tee time. The golfer taps a link and completes the booking themselves, on your site, in their own browser, under their own account.
• It never holds a reservation, never cancels one, and never resells one.
• It never stores anyone's login for a course or a booking platform.
• It never rotates IP addresses or uses proxies. All traffic comes from one static address so you can identify and block it in one rule.
• It never solves, farms or bypasses a CAPTCHA, and never touches a page behind one.
• It never reads anything behind a login, including member rates and resident rates that require an account.

Removing your course

Blocking our user-agent or our IP works too and takes effect immediately. We will treat it as permanent and will not attempt to work around it. Emailing us just means you get a confirmation and we stop wasting your bandwidth on requests that will fail.

Something else wrong?

If our reads are costing you measurably, if our timing is bad for your maintenance window, or if we have got something factually wrong about your course, write to the same address. We would rather adjust than argue, and we will tell you exactly what we changed.