The recurring decision
Developers repeatedly need a stable regulator facility identifier before storing evidence, adding monitoring, or continuing an onboarding workflow.
Why horizontal data falls short
Broad business and place APIs can return plausible locations without proving that the selected record is the supported regulator facility for the submitted address.
What Venue Authority returns
Venue Authority applies one frozen resolver policy and charges one prepaid unit for each valid authenticated resolution or canonical facility request, including a fail-closed rejection.
The API response
The response includes the disposition, reason, regulator identity, snapshot, and evidence boundary your integration needs.
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"
}