For builders of AI applications
A source you may use, from a sender you can check
Checking will not need an account. The specification will be open.
The check in six steps
- 1Find the declarationIn the file, as a companion file, on the sender’s domain, or in the register
- 2Check the fingerprintIf it differs, the declaration does not belong to this file
- 3Check the signaturesThe sender’s and the service’s
- 4Check the statusStill valid and not withdrawn
- 5Read profile and levelDoes the intended use fit, and is the level high enough
- 6Use and name the source
Planned connections
| Connection | What it does |
|---|---|
| Verification API | Fingerprint in; sender, level, profile and status out |
| MCP server | Three tools for assistants: check a declaration, find released content of a sender, fetch the content |
| Skill | Teaches an assistant to check the declaration before it uses a manufacturer’s content |
verify_declaration({ sha256: "9f2c…e41a" })
→ { issuer: "Example Climate Systems Ltd",
assuranceLevel: "organisation",
profile: "faithful",
status: "valid",
attribution: "Example Climate Systems Ltd" }The names of tools and fields are a proposal.