Start with the right place
Planned venue selection and coverage notes, so you can check whether a place has suitable aggregate data before using it.
Coming soonVENUE PATTERNS, IN CONTEXT In development
A foot traffic API.
More context for every place.
We are building a clearer way to work with aggregate venue busyness: the pattern, its time window and the coverage behind it. Join free early access. The API is not live yet.
Free to join. No card. No API or payment is live.
Explore the venue data guides ↗
PLANNED VENUE CONTEXTTypical.
Current.
Kept distinct.Product illustration · not live data
Current.
Kept distinct.Product illustration · not live data
ILLUSTRATIVE WEEKLY PATTERN
Relative activity, with its definition.
Concept only · synthetic values
Original AI-generated fictional venues and product illustrations. No measured or live foot traffic is shown.
BUILD AROUND A BETTER QUESTION
What does this place
look like over time?
We are designing for developers who need aggregate venue patterns with clear definitions. Before a score reaches your application, the planned workflow will keep its place, time context and availability in view.
PlaceCheck the venue and its coverage.
TimeDistinguish a typical pattern from current activity.
MeaningKeep relative scores separate from visitor counts.
THE PLANNED PRODUCT
Venue foot traffic data, with context
Keep time in the picture
Planned typical-pattern and current-activity fields, kept distinct with their available time context.
Coming soonKnow what a score means
Planned metric definitions and availability indicators. A relative busyness score will not be presented as a headcount.
Coming soonBuild with aggregate patterns
A planned API for venue-level patterns. Identified-person locations, journeys and individual tracking are outside our scope.
Coming soonFROM INTEREST TO ACCESS
How the planned venue API will work
- Join free early accessCreate an account and tell us you are interested. No card or payment is needed.
- Define your venue questionWhen access opens, the planned workflow will help you specify places, time windows and the kind of pattern your project needs.
- Review coverage before integratingWe plan to keep data availability and metric context visible before you build around a venue.
A CLEAR START
Plans and launch price
Nothing is for sale yet. Early access is free. Tap "Lock this launch price" on a paid plan and we'll keep that price for you when it opens. You won't be charged now.
BEFORE YOU JOIN
Questions about aggregate venue patterns
Can I call the API today?
Not yet. VenueHours is in development. Today you can join early access and record your launch-price preference. No venue lookup, API response or export is live.
Will a busyness score tell me how many people are there?
The proposed product focuses on aggregate patterns and clearly defined relative metrics. A relative score alone does not establish an absolute visitor count.
Will every venue have live data?
We cannot promise coverage or live availability. Our planned workflow will distinguish missing information from a measured zero and keep available time context visible.
Does VenueHours track individual people?
No identified-person location tracking is part of the proposed product. We are designing around aggregate patterns at public venues.
Can I get past holiday or date-specific counts?
Date-specific archives are not a confirmed feature. Typical weekly patterns, current activity and historical observations answer different questions; we will not label one as another.
What is the proposed launch price?
The proposed plan is $96 per month for 50 venues when the product launches. Reserving it today records interest only. You are not starting a subscription and nothing is charged.
Bring more context to every place.
Join free early access. We will email you when the product is ready to try.