Disclaimer

Read this before you rely on a grape fact from here.

Not an official source

Independent project. Not affiliated with, endorsed by or certified by the Alcohol and Tobacco Tax and Trade Bureau, the Office of the Federal Register, the Wikimedia Foundation, or the Vitis International Variety Catalogue.

The upstream is crowd-sourced, and it is wrong sometimes

Wikidata is edited by volunteers. Its breadth is why this service uses it and its variability is why every record here carries provenance, a link back to the entity, and a confidence score. Two errors found during construction are published at /v1/quality and are still live upstream at the time of writing:

That register is a floor on the error rate, never a ceiling. It lists what was found.

Confidence means corroboration, not correctness

The score measures how well described an entity is — whether it has a VIVC cross-reference, a species, an origin. A well-described record can still be wrong, and some of them are.

A co-occurrence claim is not a rule

Wikidata's P186 links record that an editor associated a grape with a wine. They are not permitted-variety lists, they carry no percentages, and 98.5% of them are Italian. Every claim this service returns says so in its own body. Do not build a blending calculator on them.

Where upstream contradicts itself, so does the answer

146 varieties carry berry colours that map to different categories. This service returns unknown with both raw values and an explanation rather than choosing. That is the honest answer; treating it as a gap in the data would be a misreading.

The composition rules are US law, quoted, not advice

27 CFR part 4 governs what a wine sold in the United States may be called. The thresholds are reproduced verbatim with their citations. TTB determines label approval; this is not legal advice, and it says nothing about EU appellation rules.

VIVC

Identifiers only, referenced through Wikidata P3904. No VIVC content is stored or served — VIVC grants no reuse rights. Follow the link for the authoritative passport data.

Freshness and history

Wikidata changes continuously. This service refreshes weekly, so it can be behind; every response carries datasetVersions. The retained history begins when this service began capturing, not when Wikidata did — a request for an earlier date returns 422 naming the coverage start rather than answering with current data.

No uptime commitment, and liability

One small server shared with six sibling APIs, offered as-is with no availability guarantee. The complete datasets are published as static files and the server is MIT licensed — host your own copy if you need reliability. To the maximum extent permitted by law, no warranty is given and no liability is accepted for any loss arising from use of this service.

Corrections

If something here is wrong, the right fix is usually upstream — edit Wikidata and it will flow through on the next refresh, which is the best argument for using a CC0 commons in the first place. If this service has mangled something Wikidata got right, tell me on LinkedIn.