Getting started

Glasswise exposes two machine interfaces on top of its e-label surface:

• The REST API at https://public-api.glasswise.eu/v1 is the contract partner integrations program against. It covers the workspaces (wineries) you belong to, brands, labels with their parts and bottle-size formats, marketing QR codes, and the read-only reference catalogues.
• The MCP server at https://mcp.glasswise.eu/mcp exposes the same operations as tools to MCP clients such as Claude Code. The MCP server is itself a client of the API.

A label is the digital wine label behind a bottle’s QR code: identity, ingredients, grape varieties, certifications, packagings and translations, plus one bottle-size format per GTIN. A marketing QR code is a second, editable code that resolves to a destination you choose.

First request

Every call under /v1 needs a bearer token; see Authentication. The one exception is the OpenAPI document itself:

curl https://public-api.glasswise.eu/v1/openapi.json

With a token, list the workspaces your account belongs to:

curl -H "Authorization: Bearer <token>" https://public-api.glasswise.eu/v1/workspaces

The same token works on the MCP server. Connect the MCP covers the client setup and the tool list.

Where things live

Surface	Base URL
REST API	https://public-api.glasswise.eu/v1
OpenAPI document	https://public-api.glasswise.eu/v1/openapi.json
MCP server	https://mcp.glasswise.eu/mcp
Liveness probe	https://public-api.glasswise.eu/healthz (unauthenticated)