Pricing
Month to month, cancel whenever. Limits are requests per UTC day and reset at midnight. Every plan gets the full API and the widget library; the tiers differ in volume and how fast we answer.
free
- Full API, no card
- One publishable key
- Enough to know
developer
- Side project, graduated
- Email support
- Widgets in production
starter
- Production applications with steady traffic
- Batch calls: one request per hundred operations
- Email support, one business day
pro
- Headroom for spikes and reconciliation runs
- Priority on the support queue
- Most teams start on Starter. The ones who shouldn't usually know.
business
- Platforms and ETL
- Priority support
- Usage reporting
Create a free key
Lost keys aren't recoverable (we store only a hash), but your account page can rotate and manage them any time.
Upgrade
Checkout and card handling are Stripe's, on their servers. We never see the number. Cancel any time; access drops to the free tier at period end.
Questions a careful buyer asks
What happens when I hit the limit?
429, with headers telling you where you stand. Over-limit requests
aren't billed against your count. At midnight UTC the counter resets and requests
flow again.
Is the data actually right?
It is sourced from open calendar projects, checked against independent references before each release, and organized with curated weekend rules and market calendars on top. The dataset version is public at /health. When a calculation would leave the covered range we return an error rather than a wrong answer.