Verify food-service facilities against supported regulator records.
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.
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.
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.
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.
The contract also covers canonical facility records, portfolios, audit exports, webhooks, and webhook delivery history.
The repository includes three reviewed, versioned integrations:
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.
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.
This repository contains public integration artifacts. Use of the hosted API is governed by the Venue Authority terms.
This listing does not have a supported local package template. Use the maintainer’s documentation for its hosted endpoint, authentication, and client-specific setup. No install command has been inferred.
https://github.com/kingymon1/venue-authority-api/releases/download/clients-v0.1.0/venue-authority-mcp-0.1.0.mcpbotherVenue Authority works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.