Find the regulator record
Match the merchant name and street address to the regulator's facility ID. Conflicts and close ties are rejected.
Facility verification and monitoring API
Verify food-service locations
before and after approval.
Venue Authority helps payment facilitators, marketplaces, KYB providers, and restaurant platforms match a business name and address to its local regulator record, save an audit receipt, and monitor supported changes.
34 of 39 sources are current; 5 refresh due. View source freshness.
venueauthority.com/dashboard/evaluations
Venue Authority accountServing snapshot: Sep 17, 2026, 01:10 UTC
- Records served
- 646,977
- Regulator sources
- 39
- Retained events
- 441
- Operator inferred
- No
Serving records by sourceLargest current sources, normalized for comparison
Current snapshotRecent source activity
YOAN MING GARDEN has 3 retained source events
CAJUN HALAL PLATTERS has 5 retained source events
ANGUS BARN has 1 retained source event
Evidence receipt savedSource record and snapshot linked
Public evidence example
Did this venue lose the authority to operate?
Try a receipt from the 100-example public archive.
The public form searches archived examples. Authenticated test and paid keys use the current database serving snapshots. NYC and King County history is retrieved on demand. Wake County reports source presence. Results are not legal advice or regulator endorsement.
Get the answer and the proof behind it.
Venue Authority shows the regulator record, the latest supported status signal, the history the source makes available, and the exact snapshot used for the decision.
See the food-service business verification API for the request, response, and rejection rules.
Read the status correctly
Keep explicit closure and reopening actions separate from a facility that only appears in an active-source list.
Save the receipt
Keep the request ID, source record, event dates, retrieval time, snapshot version, and SHA-256 evidence hash.
Explore Venue Authority
Find the part of the site you need.
See how the product works, find your use case, inspect the evidence, or review the controls behind delivery.
Real regulator histories, not generated examples.
Start with a verified facility record.
Resolve the facility during onboarding, keep the regulator ID, and use your account tools to follow supported source changes.
One structured response
Send a merchant and address. Receive the match decision, regulator record, status assessment, retained history where the source supports it, and a receipt. Wake County results report current source presence when history is unavailable.
Watchlists and webhooks
Add selected facilities and receive stable source events through HMAC-signed HTTPS webhooks. Paid monitoring expansion is not available yet.
Scheduled source refreshes
Each successful regulator pull is validated, hashed, and versioned before it can become active. The latest successful pull appears on the coverage page.
Portable audit exports
Bundle up to 100 stored request receipts into an account-scoped JSON export with its own SHA-256 hash.
Self-serve API access
Test the matching policy before you commit production capacity.
A new verified account can claim one 25-unit test allowance and run the same resolver used by paid keys. Six prepaid tiers range from 100 to 150,000 decisions. Larger plans cost less per decision and process requests faster.