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 6 API contracts indexed on the APIs.io network, including Audit Exports API, Coverage API, Webhooks API, and 3 more. Tagged areas include Food Service, facility verification, Merchant Onboarding, regulator records, and Monitoring.

The Venue Authority catalog on APIs.io includes 1 Spectral governance ruleset.

Venue Authority’s developer surface includes support and 16 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

42.0/100 developing ▬ flat Agent 32/100 agent ready Front door AI 2/6 trace saas Full breakdown ↓
scored 2026-11-13 · rubric v0.28.0 · Show this score on your site →

2 published contracts 1 MCP Servers

Food Servicefacility verificationMerchant Onboardingregulator recordsMonitoring KYBPayment FacilitatorsMarketplacerestaurant platforms

Kin Score

Kin Score How this is scored →
scored 2026-11-13 · rubric v0.28.0

Composite quality — 42.0/100 · developing

Contract Quality 9.9 / 19

Developer Ergonomics 10.0 / 15

Access Clarity 4.2 / 15

Operational Transparency 2.6 / 10

Contract Governance 1.2 / 9

Discoverability 4.4 / 8

Regulatory Posture 2.7 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 32/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Payments regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/venueauthority/"><img src="https://apis.io/badge/venueauthority/card.svg" alt="Venue Authority on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author Ask about this →
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented) Ask about this →
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0 Ask about this →
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document Ask about this →
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too Ask about this →

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 27.7 — up to +14.5 composite points Ask about this →
Contract Quality scores 52.8 — up to +11.8 composite points Ask about this →
Contract Governance scores 13.6 — up to +10.4 composite points Ask about this →

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/venueauthority/apis.yml: open an issue on github.com/api-evangelist/venueauthority to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
GLEIF LEI Issuers (Legal Entity Identifier infrastructure)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

OpenAPI

measured — observed by APIs.io (published)

APIs 6

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 Webhooks API

Venue Authority Facilities API

The Facilities API from Venue Authority — 1 operation(s) for facilities.

Venue Authority Portfolios API

The Portfolios API from Venue Authority — 4 operation(s) for portfolios.

Venue Authority Resolve API

The Resolve API from Venue Authority — 1 operation(s) for resolve.

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Venue Authority MCP Server

MCP SERVER

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs. Counts are the severity each rule declares, not results of running them.

Venue Authority API Rules

56 rules · 52 error-severity 1 warn-severity 3 info-severity

SPECTRAL

Resources

Get Started 1

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

Documentation 1

Reference material describing how the API behaves

PostmanDocumentation

PostmanDocumentation

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

MCPServer

MCPServer

Build 5

SDKs, sample code, and the tooling you integrate with

GitHubRepository

SDKs

SDKs

GitHubRelease

PostmanWorkspace

Access & Security 1

Authentication, authorization, and security posture

SecurityPolicy

SecurityPolicy

Operate 2

Status, limits, changes, and where to get help

StatusPage

StatusPage

Support

Support

Commercial 3

Pricing, plans, and the legal terms of use

Plans

Plans

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

APIsJSON

APIsJSON

Source (apis.yml)

aid: venueauthority
name: Venue Authority
description: 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.
type: Index
deliveryModel:
  model: saas
  license_evidence:
    not_product:
    - kingymon1/venue-authority-api
  open_source: unknown
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: low
  source:
  - openapi
  - pricing
  - repository-not-product
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-11-13'
  method: derived
image: https://venueauthority.com/venue-authority-mark.svg
url: https://raw.githubusercontent.com/api-evangelist/venueauthority/refs/heads/main/apis.yml
created: '2026-08-21'
modified: '2026-08-21'
specificationVersion: '0.23'
tags:
- Food Service
- facility verification
- Merchant Onboarding
- regulator records
- Monitoring
- KYB
- Payment Facilitators
- Marketplace
- restaurant platforms
tags_raw:
- food service
- facility verification
- merchant onboarding
- regulator records
- monitoring
- KYB
- payment facilitators
- marketplaces
- restaurant platforms
apis:
- aid: venueauthority:venueauthority-audit-exports-api
  name: Venue Authority Audit Exports API
  description: Create and download workspace-scoped evidence exports.
  humanURL: https://venueauthority.com/developers
  tags:
  - Audit Exports
  properties:
  - type: OpenAPI
    url: openapi/venueauthority-audit-exports-api-openapi.yml
  - type: PostmanCollection
    url: collections/venueauthority.postman_collection.json
  - type: ErrorCatalog
    url: errors/venueauthority-error-catalog.json
  - type: GettingStarted
    url: docs/venueauthority-quick-start.md
  - type: Documentation
    url: https://venueauthority.com/developers
  - type: APIReference
    url: https://venueauthority.com/openapi.json
  - type: Authentication
    url: https://venueauthority.com/developers
  - type: Signup
    url: https://venueauthority.com/sign-up
  - type: Webhooks
    url: https://venueauthority.com/trust/webhook-delivery
  - type: RateLimits
    url: https://venueauthority.com/pricing
- aid: venueauthority:venueauthority-coverage-api
  name: Venue Authority Coverage API
  description: Read supported sources, record counts, availability, and freshness.
  humanURL: https://venueauthority.com/developers
  tags:
  - Coverage
  properties:
  - type: OpenAPI
    url: openapi/venueauthority-coverage-api-openapi.yml
  - type: PostmanCollection
    url: collections/venueauthority.postman_collection.json
  - type: ErrorCatalog
    url: errors/venueauthority-error-catalog.json
  - type: GettingStarted
    url: docs/venueauthority-quick-start.md
  - type: Documentation
    url: https://venueauthority.com/developers
  - type: APIReference
    url: https://venueauthority.com/openapi.json
  - type: Authentication
    url: https://venueauthority.com/developers
  - type: Signup
    url: https://venueauthority.com/sign-up
  - type: Webhooks
    url: https://venueauthority.com/trust/webhook-delivery
  - type: RateLimits
    url: https://venueauthority.com/pricing
- aid: venueauthority:venueauthority-webhooks-api
  name: Venue Authority Webhooks API
  description: Register endpoints and inspect delivery attempts.
  humanURL: https://venueauthority.com/developers
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/venueauthority-webhooks-api-openapi.yml
  - type: PostmanCollection
    url: collections/venueauthority.postman_collection.json
  - type: ErrorCatalog
    url: errors/venueauthority-error-catalog.json
  - type: GettingStarted
    url: docs/venueauthority-quick-start.md
  - type: Documentation
    url: https://venueauthority.com/developers
  - type: APIReference
    url: https://venueauthority.com/openapi.json
  - type: Authentication
    url: https://venueauthority.com/developers
  - type: Signup
    url: https://venueauthority.com/sign-up
  - type: Webhooks
    url: https://venueauthority.com/trust/webhook-delivery
  - type: RateLimits
    url: https://venueauthority.com/pricing
- aid: venueauthority:venueauthority-facilities-api
  name: Venue Authority Facilities API
  description: The Facilities API from Venue Authority — 1 operation(s) for facilities.
  humanURL: https://venueauthority.com/developers
  tags:
  - Facilities
  properties:
  - type: OpenAPI
    url: openapi/venueauthority-facilities-api-openapi.yml
  - type: PostmanCollection
    url: collections/venueauthority.postman_collection.json
  - type: ErrorCatalog
    url: errors/venueauthority-error-catalog.json
  - type: GettingStarted
    url: docs/venueauthority-quick-start.md
  - type: Documentation
    url: https://venueauthority.com/developers
  - type: APIReference
    url: https://venueauthority.com/openapi.json
  - type: Authentication
    url: https://venueauthority.com/developers
  - type: Signup
    url: https://venueauthority.com/sign-up
  - type: Webhooks
    url: https://venueauthority.com/trust/webhook-delivery
  - type: RateLimits
    url: https://venueauthority.com/pricing
- aid: venueauthority:venueauthority-portfolios-api
  name: Venue Authority Portfolios API
  description: The Portfolios API from Venue Authority — 4 operation(s) for portfolios.
  humanURL: https://venueauthority.com/developers
  tags:
  - Portfolio
  tags_raw:
  - Portfolios
  properties:
  - type: OpenAPI
    url: openapi/venueauthority-portfolios-api-openapi.yml
  - type: PostmanCollection
    url: collections/venueauthority.postman_collection.json
  - type: ErrorCatalog
    url: errors/venueauthority-error-catalog.json
  - type: GettingStarted
    url: docs/venueauthority-quick-start.md
  - type: Documentation
    url: https://venueauthority.com/developers
  - type: APIReference
    url: https://venueauthority.com/openapi.json
  - type: Authentication
    url: https://venueauthority.com/developers
  - type: Signup
    url: https://venueauthority.com/sign-up
  - type: Webhooks
    url: https://venueauthority.com/trust/webhook-delivery
  - type: RateLimits
    url: https://venueauthority.com/pricing
- aid: venueauthority:venueauthority-resolve-api
  name: Venue Authority Resolve API
  description: The Resolve API from Venue Authority — 1 operation(s) for resolve.
  humanURL: https://venueauthority.com/developers
  tags:
  - Resolve
  properties:
  - type: OpenAPI
    url: openapi/venueauthority-resolve-api-openapi.yml
  - type: PostmanCollection
    url: collections/venueauthority.postman_collection.json
  - type: ErrorCatalog
    url: errors/venueauthority-error-catalog.json
  - type: GettingStarted
    url: docs/venueauthority-quick-start.md
  - type: Documentation
    url: https://venueauthority.com/developers
  - type: APIReference
    url: https://venueauthority.com/openapi.json
  - type: Authentication
    url: https://venueauthority.com/developers
  - type: Signup
    url: https://venueauthority.com/sign-up
  - type: Webhooks
    url: https://venueauthority.com/trust/webhook-delivery
  - type: RateLimits
    url: https://venueauthority.com/pricing
common:
- type: APIsJSON
  url: https://venueauthority.com/apis.json
- type: LLMsTxt
  url: https://venueauthority.com/llms.txt
- type: Website
  url: https://venueauthority.com
- type: DeveloperPortal
  url: https://venueauthority.com/developers
- type: Plans
  url: https://venueauthority.com/pricing
- type: StatusPage
  url: https://venueauthority.com/status
- type: TermsOfService
  url: https://venueauthority.com/terms
- type: PrivacyPolicy
  url: https://venueauthority.com/privacy
- type: SecurityPolicy
  url: https://venueauthority.com/trust/api-key-and-tenant-security
- type: Support
  url: https://venueauthority.com/support
- type: GitHubRepository
  url: https://github.com/kingymon1/venue-authority-api
- type: SDKs
  url: https://github.com/kingymon1/venue-authority-api/tree/main/packages/node-sdk
- type: SDKs
  url: https://github.com/kingymon1/venue-authority-api/tree/main/packages/python-sdk
- type: MCPServer
  url: https://github.com/kingymon1/venue-authority-api/tree/main/packages/mcp-server
- type: GitHubRelease
  url: https://github.com/kingymon1/venue-authority-api/releases/tag/clients-v0.1.0
- type: PostmanWorkspace
  url: https://www.postman.com/kingymon11-8337942/venue-authority/overview
- type: PostmanDocumentation
  url: https://documenter.getpostman.com/view/57620096/2sBYArVYPE
maintainers:
- FN: Venue Authority
  url: https://venueauthority.com
x-provenance:
  added: '2026-08-21'
  method: searched
  source: https://github.com/api-search/inbox/issues/12
  note: 'Submitted by the provider on the api-search/inbox issue tracker with a complete artifact list. Every declared URL
    was fetched and confirmed 2xx before being recorded here, against a control probe of two invented paths that returned
    real 404s, so the 200s are genuine routes and not a catch-all. The live API was exercised anonymously: /api/v1/coverage
    returned real regulator records, /api/v1/resolve returned 405 (it is POST-only) and /api/v1/facilities/{id} returned 401.
    Nothing in this record is derived or modelled.'
x-evidence:
  amended: '2026-08-21'
  source: https://github.com/api-search/inbox/issues/12
  note: 'The provider reported two changes on the original issue and both were re-verified live before anything here moved.
    FIRST, the contract is now tagged: the published OpenAPI declares five tags and all fifteen operations carry one, where
    the version harvested on 2026-08-21 declared none. Diffed against the archived original, the operation set is byte-identical
    — same 12 paths, same 15 operationIds, nothing added, removed or renamed — so the change is purely additive and the single
    document was re-split into five per-resource documents with 1.00x duplication and zero dangling references. The pre-tag
    upstream is kept at openapi/_original/venueauthority-openapi-2026-08-21-untagged.json. SECOND, the client packages exist:
    packages/node-sdk, packages/python-sdk and packages/mcp-server are present in the repository, each carrying its own MIT
    LICENSE, and release clients-v0.1.0 publishes four build artifacts whose SHA-256 digests are computed by GitHub rather
    than supplied by the provider. The MCP package''s declared dependencies resolve on npm at the pinned versions. npm and
    PyPI return 404 for these package names, which matches the provider''s own statement that no registry-availability claim
    is being made; no registry pointer is recorded here. Every URL added to common[] was fetched against a control probe of
    four plausible-but-absent paths (/openapi.yaml, /sdk, /docs/changelog.json, /.well-known/security.txt) that all returned
    real 404s, so the 200s are genuine routes.'
  not_recorded:
  - The provider's apis.json declares maintainers[0].organizationName "Zupa Print", which does not match any other Venue Authority
    surface. Left out of maintainers here pending confirmation from the provider rather than recorded as the operating entity.
  - https://venueauthority.com/.well-known/apis.json returns 404. The apis.json copy held under well-known/ in this repo is
    a harvest of https://venueauthority.com/apis.json, not evidence of a .well-known catalog, and is not scored as one.

Venue Authority API — frequently asked questions

Does Venue Authority have an API?

Yes. APIs.io lists 6 APIs from Venue Authority, including Venue Authority Audit Exports API, Venue Authority Coverage API and Venue Authority Webhooks API, and 3 more.

Is there an OpenAPI specification for the Venue Authority API?

Yes. APIs.io indexes 6 OpenAPI specifications for Venue Authority, each linked for download from this page.

How do I authenticate with the Venue Authority API?

Venue Authority uses bearer-token authentication.

Does Venue Authority have an MCP server?

Yes. APIs.io lists 1 MCP server for Venue Authority.

Is the Venue Authority API ready for AI agents?

Venue Authority has a Kin Score of 42.0 out of 100 (developing) and an Agent Readiness score of 31.8 (agent-ready), scored by API Evangelist on 2026-11-13.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/venueauthority"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/venueauthority/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/venueauthority/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.