Expand, parse, build and describe iCalendar RRULE recurrences, plus weekday and business-day patterns.
payments ON MAINNET (real money) · 8 live endpoints
| Endpoint | Price | What it answers |
|---|---|---|
GET /business-recurrence | $0.03 | Dates for every N business days, or the last or Nth business day of each month, skipping weekends and your holiday list. |
GET /next-occurrence | $0.02 | First occurrence of an iCalendar RRULE strictly after a given date-time, honoring EXDATE and a fixed UTC offset. |
GET /nth-weekday-of-month | $0.02 | Dates of the Nth weekday (or last) of each month in a year, e.g. second Tuesday of 2027; months without one are listed. |
GET /occurrences-between | $0.02 | List every occurrence of an iCalendar RRULE inside a date range (from and to inclusive), capped at 366 per call. |
GET /rrule-build | $0.02 | Build a validated RRULE string from fields (freq, interval, byday, bymonthday, bysetpos, count or until) with a check. |
GET /rrule-describe | $0.02 | Turn an iCalendar RRULE into one plain English sentence (every other week on Tuesday and Thursday, 8 times). |
GET /rrule-expand | $0.03 | Expand an iCalendar RRULE from DTSTART into the next N dates (max 366), with EXDATE, BYDAY ordinals, BYSETPOS and WKST. |
GET /rrule-parse | $0.02 | Validate an RRULE string against RFC 5545 section 3.3.10, list every error and warning, and explain it in English. |
GET /catalog returns this list as JSON. Activity hub · uptime.
Dates are computed from RFC 5545 rules in floating local time with a fixed UTC offset you supply; no time zone database or daylight saving rules are applied. Hourly, minutely, secondly and BYHOUR/BYMINUTE/BYSECOND rules are not supported. Not legal, payroll or contractual advice; check holidays and cut-off dates against official sources. Every paid response carries a disclaimer field.