What a verified card means

A verified card is a disclosure record. This page lists every field it can carry, says what a tick does and does not mean, and shows how much of the catalogue is covered today.

LLM EU Verified means documented, not legally certified. It is not an AI Act conformity assessment and LLM EU is not an EU body.

A tick means documented, not audited

A tick says that the endpoint row records a value for that field and that the value can be read on the card. It says nothing about who checked it, whether it is correct, or whether it will still be true tomorrow. There is no independent audit behind a tick. A field with no source is left unticked and named in missing_items rather than filled in.

No certification, no third-party assessment, no compliance stamp

LLM EU Verified is not a certification and not a compliance stamp. No third-party assessment has been carried out, no conformity assessment exists, and LLM EU is a private company rather than a supervisory authority or an EU body. This is ADR-006 in docs/product/decisions.md: the product never claims a certification, and the value of a European hub is that its claims survive a data protection officer reading them. A reader who needs an assurance a tick cannot give should treat the linked documents as documents and nothing more.

Every field a card records

Ten fields, read from the verified_cards table in packages/shared/src/db/schema.sql. The six ticks are stored as 0 or 1; the four URLs are stored as links, and an empty one is the absence of that document.

Field in verified_cards What it records
residency_disclosed The endpoint's own residency: its region and sovereignty class, read from the endpoint row and not from the model card.
provider_disclosed The provider of the weights, so the entity behind the model is named rather than implied.
version_pinned The pinned model version the endpoint serves, so a claim is about a version and not about a moving tag.
retention_disclosed What happens to a prompt on that endpoint. Zero retention means the prompt and completion bodies are never written to the database.
subprocessors_disclosed Whether the subprocessors behind the endpoint are disclosed. The inventory is incomplete, and the legal page says so.
license_disclosed The licence recorded for the weights, with the identifier and, where one is recorded, the URL of the licence text.
security_docs_url A link to a security page the provider publishes. A document, not a finding.
gdpr_docs_url A link to the provider's GDPR or privacy page. A document, not a finding.
ai_act_docs_url A link to an AI Act notice. A document, not a conformity assessment and not evidence of one.
language_evidence_url A link to evidence for the languages the model claims. Without a source the claim is published as unverified.

missing_items is published, not hidden

missing_items is the list of fields the review recorded as still missing for an endpoint. It is a record of a gap, not a failure state, and it is shown on the card rather than suppressed. A field can be both stored and listed as missing, and where that happens this page shows both rather than reconciling them.

Field recorded missing Cards listing it
ai_act_docs_url 6 of 6 cards
language_evidence_url 6 of 6 cards
subprocessors_disclosed 6 of 6 cards

Recorded as missing while also carrying a value: ai_act_docs_url. Both are read from the row as it stands; this page does not reconcile them.

How much of the catalogue carries a card

6 of the catalogue's 53 endpoints carry a verified card; 47 do not. The count is read from the endpoint rows at render time, so it moves with the catalogue instead of being asserted here.

Coverage is not quality. An endpoint without a card is not a negative finding: it is an endpoint nobody has written the disclosures for yet, and the absence of the card is the honest state.

Basis: packages/shared/src/db/schema.sql (verified_cards), apps/web/server/pages/public.mjs (verifiedChecklist), scripts/seed.mjs (which endpoints get a card), docs/product/decisions.md (ADR-006).

Verified →