New Opening Permit Lead Radar
Pricing
Pay per event
New Opening Permit Lead Radar
Detect commercial permit and license openings from five fixed Socrata datasets and return evidence-backed signals.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Tim Zinin
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
2 days ago
Last modified
Categories
Share
Find recent commercial opening signals in five fixed public city datasets and return ranked permit or business-license leads with source IDs, addresses, dates, scores, and observed source-field evidence. The actor is bounded, deterministic, and designed for scheduled lead research.
What you get
- Commercial permit and license signals from Chicago, New York City, Los Angeles, Seattle, and Austin.
- Stable dedupe keys, deterministic ranks, recency and opening scores, and source metrics.
- Evidence for the observed business, address, event date, description, and status fields.
- Bounded pagination, retries, redirects, request replay protection, and compact OUTPUT metadata.
- Dataset rows are billed only after linked result delivery succeeds.
- Runs on Apify: schedule it, monitor it, call it from the API, and export JSON, CSV, or Excel.
How to run it
- Click Try for free and open the Input tab.
- Set schemaVersion to 1.0 and optionally choose lookbackDays, maxResults, and freshnessMinutes.
- Click Start, then read useful rows from the Dataset and the compact envelope from the OUTPUT key-value record.
Pricing
Pay-per-event: $0.005 per run start + $0.03 per useful result. No monthly seat. Empty, invalid, unavailable, budget-stopped, and undelivered results are not charged as useful rows. Ten useful rows cost $0.30 in result events, plus the start event.
Input
{"schemaVersion":"1.0","requestId":"permit-demo-001","maxResults":10,"freshnessMinutes":60,"detailLevel":"compact","lookbackDays":30}
Output
{"schemaVersion":"1.0","requestId":"permit-demo-001","status":"ok","results":[{"dedupeKey":"stable-key","rank":1,"score":91}],"errors":[],"metadata":{"resultCount":1,"datasetWriteCount":1,"billedResultCount":1}}
Useful Dataset rows include sourceId, sourceRecordId, businessName, address, eventDate, commercialScore, openingScore, signalScore, evidence, and sourceMetrics.
Related tools
Related tools for adjacent workflows in operational gap-lead generation.
| Actor | What it does |
|---|---|
| EU Accessibility Privacy Lead Scanner | Pair it in the operational gap-lead generation workflow: BYOD compliance scanner for observed accessibility and privacy exposure signals on a submitted URL.... |
| EU AI Act Transparency Lead Scanner | Pair it in the operational gap-lead generation workflow: BYOD compliance scanner for observed AI transparency signals on a submitted URL. Deterministic,... |
| Clinic Reception Gap Lead Finder | Pair it in the operational gap-lead generation workflow: Analyze submitted clinic websites for reception-channel gaps with exact BYOD crawling and no discovery |
| Restaurant Booking Gap Lead Finder | Pair it in the operational gap-lead generation workflow: Analyze submitted restaurant websites for booking-channel gaps with exact BYOD crawling and no discovery |
FAQ / Limitations
Does it discover businesses? No. It reads only the five fixed public datasets and does not accept source URLs.
Why can a recent row be absent? A row needs a valid source identity, address, event date, commercial signal, active/opening signal, and a date inside the requested lookback.
What is this not? It is not a permit approval, legal, construction, or investment decision service. Verify important records with the issuing authority.
How is duplicate work controlled? Cloud runs use the named RequestQueue unique key; local storage tests verify persistence, while local RequestQueue concurrency remains a platform-specific residual.
Need help? Check the run log and OUTPUT errors first, then report the request ID and source ID on the Actor page.
