What does the facility signal establish?
The signal establishes which supported regulator record cleared the frozen name and address resolver policy. It does not establish beneficial ownership, legal operator identity, or a regulator endorsement.
For KYB data providers
Embed a local food-facility regulator signal.
Complement entity-level KYB with a fail-closed facility match from supported local regulator sources.
The recurring decision
KYB data providers repeatedly decide which local evidence can be attached to a business record without overstating what that evidence proves.
Why horizontal data falls short
Corporate registries and broad business datasets usually operate at entity level. Food-facility regulation often uses a different identifier, address grain, and update history.
What Venue Authority returns
Venue Authority supplies a regulator record, source identifier, evidence hash, snapshot time, and explicit limitations through a metered API response.
Production-compatible API shape
The response shape can sit beside entity-level data while keeping the facility signal and its limitations separate.
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"
}Questions buyers ask
Can the response be audited later?
Yes. Completed metered requests create immutable evidence receipts. A workspace can request a JSON audit export that includes owned receipts, response hashes, snapshot references, and manifest identity.
How is replay handled?
A stable request ID with the same canonical payload returns the stored response without a second debit. Reusing that request ID for different work returns HTTP 409.
Measure your own sample before choosing capacity.
Portfolio Proof uses the same resolver policy and returns bounded aggregate evidence without storing the uploaded CSV.
Run Portfolio Proof