The recurring decision
Portfolio teams repeatedly decide whether location records still point to the same regulator facilities and whether a supported source has changed.
Why horizontal data falls short
Internal location files drift. Names change, addresses vary, and a place listing rarely preserves the regulator identifier needed to compare source snapshots.
What Venue Authority returns
Venue Authority resolves facility identity, stores metered evidence receipts, and tracks supported changes for canonical records added to an account watchlist.
The API response
The response gives your workflow the canonical regulator identity needed before a location enters a watchlist.
curl -X POST https://venueauthority.com/api/v1/resolve \
-H 'Authorization: Bearer YOUR_ONE_TIME_KEY' \
-H 'X-Request-Id: onboarding-000001' \
-H 'Content-Type: application/json' \
--data '{"name":"REDACTED MERCHANT","address":"REDACTED STREET ADDRESS"}'
{
"disposition": "accepted",
"reason": "The name and address clear the corpus resolution policy.",
"record": {
"jurisdiction": "nyc",
"sourceId": "REDACTED",
"name": "REGULATOR-REPORTED NAME",
"sourceUrl": "https://data.cityofnewyork.us/..."
},
"snapshot": {"manifestSha256":"...","schemaVersion":"runtime-corpus/v1"},
"requestId": "onboarding-000001"
}