Does Venue Authority replace entity-level KYB?
No. Venue Authority adds a local facility regulator signal to an existing merchant review. The API does not establish the legal operator, beneficial owner, or corporate registration behind a trade name.
For payment facilitators
Resolve a food-service merchant name and address to the local regulator record behind the facility.
Payment facilitators repeatedly decide whether a submitted food-service location has a regulator record that supports the onboarding file.
Entity records identify companies. Place listings identify consumer destinations. Neither one establishes which local regulator record belongs to a submitted facility.
Venue Authority returns a fail-closed match decision, regulator identifier, source link, snapshot identity, and retained evidence where the source supports it.
The response shape gives an onboarding system a regulator record and the evidence boundary for the decision.
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"
}No. Venue Authority adds a local facility regulator signal to an existing merchant review. The API does not establish the legal operator, beneficial owner, or corporate registration behind a trade name.
The resolver rejects materially tied candidates and conflicting addresses. A rejected result still records the policy reason, request ID, snapshot identity, and evidence boundary for review.
Yes. A workspace can add canonical regulator records to a watchlist. Venue Authority records supported source changes and sends signed webhook deliveries with stable event identifiers and bounded retries.
Portfolio Proof uses the same resolver policy and returns bounded aggregate evidence without storing the uploaded CSV.
Run Portfolio Proof