You made something. Here's how you tell people how it was made.
When you make something, whether that's an article, some code, a design, or a document, people increasingly wonder: did a person make this, or did AI? Honestly, it's getting harder to tell just by looking. attest lets you be upfront about it.
You attach a small signed record to your work that says how it was made: by you alone, with AI help, or entirely by AI. Someone can verify that record later because it's cryptographically signed, so it can't be faked after the fact.
There's nothing to sign up for, it's just an open API you can hit whenever you want. Completely free.
| type | what it means | when you'd pick it |
|---|---|---|
| human | a person wrote this, start to finish | no AI touched it at all |
| collab | a person and AI worked on it together | you directed, AI helped, or the reverse |
| ai | AI generated this | a model produced the content with minimal human input |
If your AI agent can't browse the web, copy this prompt and paste it into your conversation. It contains everything the agent needs to know about attest and will walk you through creating an attestation together.
If your agent can install packages, use the attest-client SDK instead: npm install attest-client
The tool/interface the model was used through
The short version: you give us something (a file, a URL, or just a name) and tell us who made it. We hash it, sign it, and give you back a little JSON receipt you can stick wherever you want.
Start by picking a file to upload or pasting a URL. If you just want to register a name without content, that works too. Then choose whether it was human, collab, or AI. We'll SHA-256 hash whatever content you gave us and sign the whole thing with HMAC. You get back a signed attestation along with a shareable link that anyone can use to verify it. From there, put it wherever makes sense: an HTML meta tag, a commit message, markdown frontmatter, or a JSON sidecar file.
Verification happens entirely client-side. Nobody has to trust us, the math checks out on its own.
Wherever works for you. Here are some ideas:
| method | example |
|---|---|
| HTML meta tag | <meta name="attestation" content="{base64}"> |
| Markdown frontmatter | attestation: https://attest.97115104.com/s/ID |
| JSON sidecar | /attestations/filename.json |
| Commit message | just append the verify URL |