About Venue Authority
Venue Authority is an API and set of client integrations for payment facilitators, marketplaces, KYB providers, and restaurant platforms verifying food-service locations. Decisions link supported regulator sources to evidence boundaries, providing an auditable result while rejecting uncertain matches.
Key features
- 01Resolve merchant names and addresses
- 02Return source-linked decisions and evidence
- 03Check regulator coverage and freshness
- 04Manage facility records and portfolios
- 05Export audits and handle webhooks
- 06Node.js, Python, and MCP integrations
Use cases
- 01Verify restaurant locations during onboarding
- 02Review the regulator coverage before submitting records
- 03Keep audit evidence for facility decisions
MCP support
The included MCP server exposes public coverage, facility resolution, and canonical facility evidence to MCP hosts.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEVenue Authority API
Venue Authority checks a food-service merchant's name and street address against supported US regulator records. Each decision includes the matched source and evidence boundary, so merchant onboarding teams can keep an audit receipt instead of relying on an opaque yes or no.
It is built for payment facilitators, marketplaces, KYB providers, and restaurant platforms that need to verify locations during onboarding. Watchlist and webhook operations are documented for supported workspaces. Paid monitoring expansion is not available yet. Check current availability on the status and pricing pages.
Check coverage first
The coverage endpoint does not require an API key:
curl https://venueauthority.com/api/v1/coverage
The response shows the jurisdictions, regulator sources, source classes, and freshness state currently available to the API. Check it before sending merchant records.
See a decision before signing up
Open the public Portfolio Proof example to inspect a source-linked accepted decision, a rejected decision, and the evidence boundary. The fixed example does not require an account or upload a file.
Test a decision
- Create a verified workspace.
- Create a test key in the dashboard. An eligible verified workspace receives a one-time allowance of 25 test units.
- Send a merchant name and street address with a stable request ID.
curl -X POST https://venueauthority.com/api/v1/resolve \
-H 'Authorization: Bearer YOUR_ONE_TIME_KEY' \
-H 'X-Request-Id: quickstart-000001' \
-H 'Content-Type: application/json' \
--data '{"name":"MERCHANT NAME","address":"STREET ADDRESS"}'
A valid decision returns the disposition, policy reason, source identity, source class, source attribution, snapshot, and evidence boundary. Replaying the same request ID with the same payload returns the stored result without another debit.
Integration files
The contract also covers canonical facility records, portfolios, audit exports, webhooks, and webhook delivery history.
Client packages
The repository includes three reviewed, versioned integrations:
- Node.js SDK for Node 18 and later. It has no runtime dependencies.
- Python SDK for Python 3.9 and later. It uses only the standard library at runtime.
- MCP server for MCP hosts that need public coverage, facility resolution, or canonical facility evidence.
The v0.1.0 release includes a one-click MCP bundle and downloadable archives for all three clients. npm and PyPI releases will be documented here only after the corresponding registry publication succeeds.
Product boundaries
Venue Authority resolves a submitted facility to a supported regulator record. It does not infer the legal operator, prove that a business is physically open, or search outside the coverage returned by the API. Uncertain matches are rejected.
Links
This repository contains public integration artifacts. Use of the hosted API is governed by the Venue Authority terms.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.