Venue Authority
Venue Authority is a self-serve facility verification and monitoring API for payment facilitators, marketplaces, KYB providers and restaurant platforms working with food-service businesses. It matches a business name and street address to a supported regulator facility record, returns source-linked evidence for that match, and supports ongoing portfolio monitoring so a change at the regulator surfaces after onboarding rather than at the next manual review. The public contract is an OpenAPI 3.1 document of 12 paths and 15 operations, authenticated with a bearer API key, and the provider tags every operation into five groups — resolution and evidence, coverage, watchlists, webhooks and audit exports — which is how it is carried here as five per-resource documents. Coverage is enumerated by the API itself rather than described in prose, and the provider publishes an APIs.json, llms.txt, llms-full.txt, a Postman collection and a machine-readable error catalogue alongside the contract, plus MIT-licensed Node.js, Python and MCP client packages released on GitHub with checksummed build artifacts.
Venue Authority publishes 5 APIs on the APIs.io network, including Audit Exports API, Coverage API, Resolution & Evidence API, and 2 more. Tagged areas include Food Service, facility verification, Merchant Onboarding, regulator records, and Monitoring.
Venue Authority’s developer surface includes support and 16 more developer resources.
Kin Score
APIs 5
Individual APIs this provider publishes, each with its own machine-readable definition.
Venue Authority Audit Exports API
Create and download workspace-scoped evidence exports.
Venue Authority Coverage API
Read supported sources, record counts, availability, and freshness.
Venue Authority Resolution & Evidence API
Resolve a merchant and retrieve its canonical regulator record and retained evidence.
Venue Authority Watchlists API
Manage workspace-owned facility watchlists and stable change history.
Venue Authority Webhooks API
Register endpoints and inspect delivery attempts.
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
Venue Authority MCP Server
MCP SERVERResources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.