Without a key
Everything the page shows: the grade, every clause check, the counts, the fields present and missing, and up to four recommendations named the way a person would say them. Thirty calls per address every ten minutes.
One address measures any Digital Product Passport against the published EN standards: yours, a supplier’s, a competitor’s. The endpoint fetches the passport, negotiates content the way EN 18216 requires, and scores what comes back. It measures; it does not endorse.
curl "https://www.widinx.com/api/measure?url=https://pangaia-dpp.widinx.com/01/02611020002011/10/MWT26-0420"Response excerpt · November 4, 2026
{
"gtin": "02611020002011",
"grade": "B",
"overall": 81,
"system": { "score": 89, … },
"header": { "score": 100, … },
"content": { "score": 56, … },
…
}Returns a grade and a score for the system, the passport header and the content.
This site publishes demonstration passports for real products. Below is what the endpoint returned for one of them, in full, on the date shown. Each demo passport now answers machines too, with its public data as JSON and a GS1 linkset; the measurement also says what it still lacks, such as an independent back-up host and the fields its data does not hold: that is the point of a measurement.
Addresshttps://noo-paris-dpp.widinx.com/01/02611020001038/10/WLLB-PE26-0223GTIN 02611020001038
A measurement of what the address serves, by key name and clause. Not a legal verdict and not an endorsement: a passport that names its fields differently can read as incomplete while it is complete.
Written into this page as a snapshot on November 4, 2026. Run it again with the form below and compare.
Paste any passport address. No account, and it works on passports published by anyone: the endpoint has no idea whose platform it is looking at. The address is fetched once and kept nowhere.
One GET returns a grade, the ten clause checks, the passport-header score under EN 18223 Table 1 and how many of the ESPR-style fields are populated. CORS is open, so a browser can call it directly.
curl "https://www.widinx.com/api/measure?url=https://pangaia-dpp.widinx.com/01/02611020002011/10/MWT26-0420"Everything the page shows: the grade, every clause check, the counts, the fields present and missing, and up to four recommendations named the way a person would say them. Thirty calls per address every ten minutes.
Ten system clauses from EN 18216, EN 18219, EN 18220, EN 18221, EN 18222, EN 18223 and EN 18246; the four header attributes of EN 18223; sixteen content fields detected by key name in the JSON the address serves.
It does not read a passport behind a login, store the address, follow more than five redirects or read more than two megabytes. It never says a passport is compliant: it says what the address serves.
Filling in a passport means finding forty or so facts scattered across a PIM, a supplier’s spreadsheet and an emailed certificate. That is searching, and people already do their searching in Claude, ChatGPT and Cursor.
A WidinX MCP server will put these tools there. It is announced, not open: it is not accepting connections yet. Book a demo and ask to be told when it opens.
Anything that would be published goes back to a person first. Nothing an assistant proposes reaches a public passport without an approval in WidinX.
Products, variants, batches and the fields each grain needs, as the console holds them.
Column to field, with the document or row the value came from shown next to it.
Per product and market: the fields a passport still lacks, in the words of the sector template.
The endpoint above, as a tool call: an address in, the clause checks and the gaps out.
Tell us which products, which markets and which deadline. We come back with an honest read and a first step — usually a pilot on your real catalogue.