Sustainability

It knows what’s substantiated.

Every claim gets its own verdict, and none of them get added up. A material either meets a claim, falls short of it, asserts it without evidence, or has never been asked — and those last two are different findings, only one of which is the brand’s to answer for.

Four verdicts. No score, ever.

A single sustainability number would have to blend certifications, declarations, and absences into one figure — and blend is exactly what a specifier can’t defend. The graph keeps each claim separate, with its own verdict and its own evidence.

Meets

The claim is held and the evidence on file supports it.

Falls short

The claim was asked of the material and the record answers no.

Asserts without evidence

The brand states the claim; nothing on file substantiates it. This one is the brand's to answer for.

Never asked

The claim has not been put to this material — a different finding from an unsubstantiated assertion, and treated differently.

15 claim families on the record, 40 more programmes certifiable.

These are held claim families — typed values on material records, queryable cross-brand like any other specification.

Cradle to CradleGREENGUARD GoldEPDHPDDeclare Red List FreeLiving Product ChallengeOEKO-TEX Standard 100FloorScoreBIFMA LEVELGlobal Recycled StandardResponsible forestryISO 14001CDPH low-emittingJUSTSustainability action plan

Honesty

Bounded by the evidence on file.

A verdict is only as good as the record behind it. Claims carry their evidence — the certificate, the declaration, the test — and a claim with nothing behind it says so, rather than borrowing credibility from the ones that do.

“Never asked” is not a failure. Most materials have never been put to most claims, and the graph says exactly that instead of counting silence against anyone.

For machines

Claims are specifications. Query them like one.

Certification programmes ride the same cross-brand specification search as fire ratings and dimensions. An agent discovers the live claim vocabulary first, then filters by it — canonical tokens, not free text.

Explore the developer surface →
cURL
curl "https://beta.materialgraph.com/api/v1/catalog/specifications/facets" \
  -H "Authorization: Bearer mg_read_..."