Public Beta
REST API · MCP · UCP · JSON Schema — one vocabulary, every way in

Read the specification by machine

Everything on this site is also an endpoint. Reading needs no key.

REST API
https://api.ptpge.org/v1/ (open, no key) · version.json, scheme, openapi.json, and every term URI → JSON-LD. Read →
MCP
https://mcp.ptpge.org/mcp (open, no key; Streamable HTTP). Tools: search terms · get term · product envelope · resolve colour notation · validate configuration · fingerprint · expand fingerprint · check domain.
Add it to your assistant
Claude: switch it on in the connector directory, or (web or desktop): Settings → Connectors → Add custom connector → paste https://mcp.ptpge.org/mcp. No login. ChatGPT: Settings → Connectors → Add (developer mode) → same URL. Claude Code: claude mcp add ptpge --transport http https://mcp.ptpge.org/mcp. Then ask, in any language: «What is a roll fold?» or «Fingerprint an A4 tri-fold brochure, 170 g silk, 4/4».
Playground
ptpge.org/playground — watch an agent run the loop from a free-text order to a fingerprint, every tool call in the transcript.
Mapping
ptpge.org/mapping — drop a screenshot, a URL, a quote or an order and every option is matched to the specification, green when sure, red when you must pick. Drop a print-ready PDF and the file itself is read: trim size, orientation, pages, inks and output intent become rows «from file»; what a file cannot say (binding, paper, finish, quantity) stays red. Read in memory on mcp.ptpge.org/artwork, never kept.
Does an agent find you?
ptpge.org/check — paste a domain: fetches what a checkout agent fetches (manifest, declaration, identity), validates each against its schema, and says what the agent sees and what is missing. Also as JSON (mcp.ptpge.org/check.json?domain=…) and as the MCP tool ptpge_check_domain.
Storefronts, UCP, WebMCP
How a shop exposes PTPGE identities to agents — a UCP manifest with the fingerprint on the line item, WebMCP tools in the page. The UCP capability org.ptpge.print.identity is specified at ptpge.org/ucp. Reference: the pilot printer Trykkverk.
For models
ptpge.org/llms.txt summarises the specification for language models.
Schemas
The five document types the vocabulary is used in — vendor declaration, supplier catalogue, request, quote, UCP manifest — each with a schema under ptpge.org/v1/schemas/. Read →
Registers
Two registers live beside the vocabulary, with the same URI guarantees but counted apart: Suppliers (16 makers of presses, printers, finishing lines and paper) and Vendors (3 — the pilot printer first). An entry is an identity; what the organisation makes or offers is declared in its own document.
Conformance
PTPGE Ready — the mark for software that computes, validates, resolves, carries or writes identities and documents correctly. Public vectors, a document validator (POST mcp.ptpge.org/validate-document), free, version-bound. Read →
Writing
Proposing terms: post@ptpge.org. Claiming a supplier or vendor identity — one permanent URI, your document on your own domain: ptpge.org/adopt.

Walk through the specification

… or see it in production at the pilot printer — Trykkverk →