Vetomon Pass developer resources

The public API requires no authentication and returns product information, curated documentation, and a basic web-service status. Every published operation has a unique operation ID, typed parameters, response schemas, and descriptions suitable for generated clients and LLM function calling.

• OpenAPI 3.1 specification
• Product information endpoint
• Public resource endpoint
• Basic web-service status endpoint

Unknown API paths, unsupported methods on the three OpenAPI-listed routes, and invalid public resource identifiers return an HTTP error status with an application/problem+json body. These responses include a stable code, human-readable detail, and a recovery hint pointing back to the OpenAPI contract.

Authenticated vendor, staff, customer, Wallet, webhook, and operator endpoints are not a public integration API. Their omission is intentional: discovery metadata must not imply authorization or expose tenant and customer records.

Connect to https://vetomon.com/mcp with Streamable HTTP. The server supports the stateless 2026-07-28 request model and the 2025 initialize-based compatibility model. It exposes read-only product information as a tool and curated Markdown and JSON documents as resources.

• MCP Registry server metadata
• MCP server card
• Compatibility discovery document
• Agent instructions

Use the public API or MCP server when an agent needs to decide whether Vetomon Pass fits a service-business loyalty rollout, explain the Wallet and staff workflow, find official contact or privacy information, or discover the supported public machine interfaces. Contact Vetomon before assuming that private loyalty operations, webhooks, bulk exports, or self-service vendor provisioning are available.