How we check your work
Machines check what they can see. People confirm the rest. Every check is recorded, and anyone can check it again.
From your work to a credential
Show it's yours
Connect the account where the work lives, like GitHub, your website or a Google Doc. If we can't tell it's yours, the machine checks don't count.
Machines check the facts
Software checks what it can see: the code has a real history, the site is live, the rating is real. Each check is saved with what it saw.
AI gives feedback, for adults only
For an adult's public code, an AI scores the work and must quote the code it judges. It's feedback for you. It never decides whether your work is verified, and it's never used for anyone under 18.
People confirm the rest
Only as many people as the work needs. None when a machine can confirm it. One after a machine check. A supervisor, or two people, for work only people can see. Three for big final projects.
Every step is sealed
Each check and each confirmation is digitally signed and linked to the one before it. If anyone changes a record later, the seal breaks.
Everything goes in a public log
Every seal is added to a public log that can only grow. Anyone can check that a seal is in it.
You get a credential
Your proof becomes a digital credential that other badge and credential systems can read. Only for public work by adults.
Anyone can check it without trusting us
Developers can read seals, the log and credentials through our free API.
So far
- 7seals signed
- 7log entries
Live counts. We hide any that are zero.
Developer guide · Public log · Trust and safety
For developers: the standards we use
- Signatures: Ed25519 over RFC 8785 canonical JSON.
- Log: an RFC 9162-style Merkle log with signed tree heads.
- Credentials: W3C Verifiable Credentials 2.0 and Open Badges 3.0, with eddsa-jcs-2022 proofs, issued by did:web:powstik.com.
- Access: REST API, OpenAPI 3.1 and a read-only MCP server.