Human only
No AI in the making, or only spelling-level help.
- An essay you wrote, with a spell-checker fixing typos.
- A photo you took and edited yourself.
A free badge for your site, repo or post. You choose the label. Your visitors are never tracked.
Who produced most of the final words, code or images?
No AI in the making, or only spelling-level help.
A person produced a real share of the final work, and AI helped.
AI produced most of the final work. A person directed, chose and checked it.
Torn between two? Choose the one with more AI. Being open is the point.
You choose the label. It is your own statement, not a certificate. The bar shows the label, not a measured share.
Most badges about AI ask one question: did a machine touch this?
Made Openly asks another: is the maker honest about how it was made?
Using the tool is not the problem. Hiding it is.
Wearing the badge says: this was my hand, and the machine carried it.
Your badge is ready
Paste this where the badge should appear.
You asked to be named. Once the badge is found and approved, your place appears on the list.
Their editors don't take the code above. Add the badge as an image instead:
It counts when a reader clicks it, or when we find the link on your page.
You'll need it to remove or change this badge. We only show it now.
Your site switches between light and dark? Use this version instead.
Email signature, LinkedIn, or a site that won't take SVG? Use this PNG version. It counts the same way.
Using an AI coding assistant? Paste this prompt into it, in your project, and it adds the badge for you.
For a PDF, video or app store page, download the plain badge as SVG or PNG. It has no tracking and is never counted.
· · ·
Of these, 0 came without a token, and 0 of them may count twice. See every number
This counts places wearing the badge, not visitors. A place is active while we can see the badge there, through its image loading, a click on it, or by finding it on the page. We show every place that was added, including the ones we can't see.
You decide. Ask: who produced most of the final words, code or images? Mostly AI: AI produced most of the final work. A person directed, chose and checked it. Human + AI: A person produced a real share of the final work, and AI helped. Human only: No AI in the making, or only spelling-level help. The bar shows the label, not a measured share. The badge is a statement from its maker, not a certificate.
No. It counts places, not people. It stores no IP addresses and sets no cookies.
The place (site, repo or page address), the badge you chose, and the days it was seen. Nothing about the people who visit.
Take the badge off your page and it stops counting within a month. We keep a small record (the place, the label, the days it was seen), so it counts again if the badge comes back. To remove it completely, open madeopenly.com/manage with your badge key. No key? Write to us and we'll remove it.
It isn't needed. The badge is the record, and taking it off is how you leave.
Each place counts once a day at most, and only while we can see its badge: its image loading there, a click on it from there, or our check finding it on the page. Visits are never counted.
It depends on how the badge reaches us. The counter shows each step.
If you give a page address when you press Generate, your place shows in "added" and "not verified yet" right away. Without an address, it shows once the badge first loads on your site. A badge that is never put anywhere is removed after 30 days.
On a website you run, the badge image loads from madeopenly.com. The first load from your site ties the badge to it, and your place becomes active. You do not need to do anything else. This is the strongest sign, because it means the badge is really on the page.
Substack, Medium, Notion and GitHub copy images to their own servers, so we never see the badge load. For these, give the page address when you generate. Your place waits in "not verified yet" until we can confirm the badge is there: GitHub through its API, other pages when they let us read them, or the first time a reader clicks your badge.
If we see no sign of a place for 30 days, it moves to "not seen lately". It is kept, not deleted, and it counts again the next time we see it.
So: on your own website, just paste the snippet. On Substack, Medium, Notion or GitHub, add the badge and give the page address.
On a website, the image loading from madeopenly.com is how we know the badge is there. Each load tells us your site still wears it. We keep one mark per badge per day, and nothing about the visitor: no cookies, no IP address.
Some sites tell browsers not to say where a request comes from. Then the load cannot tie the badge to your site. Give the page address when you generate, and our check will find it.
You can download the image and host it yourself. It looks the same, but we will not see it load. Keep the link and give the page address, and our check can still find your badge. A reader's click counts too.
The token is the code in your badge address and badge link. It ties a badge to your place, and it comes with a key you can use to remove it.
A badge with no token still counts on a website. We count it by the site it loads on and the label it shows, once a day, like any other place. The counter shows these places as their own number, so you can see how many came without a token.
If you later add a badge with a token to the same site with the same label, both records are kept. Nobody can take over a place, and we never move one place's history to another. Once our check finds your token on your page, the counter counts that site and label once. Until then it may count twice, and the counter says how many.
If someone copies your snippet onto another site, the badge shows there too. It counts for their site as a place without a token, not for yours, and it does not change your count.
A reader who sees "Human + AI" should be able to find out what it means and who decided. The link takes them there.
It also helps us count. On platforms that copy the image, a reader's click is often the only way we learn the badge is there. The click tells us which site it came from. The copied image does not. The link also holds your badge's token, so our check can find it on your page.
We record nothing about the person who clicks. The click counts your place, not them.
You can remove the link and keep the image. On your own website and in a GitHub README it still counts. On Substack, Medium or Notion it may never count.
Yes. Paste the page address when you make the badge. GitHub takes the code as it is. Substack, Medium and Notion don't take code: download the badge PNG, add it as an image, and link it to your badge link (madeopenly.com/?t=…). It counts when a reader clicks it, or when we find the link on your page.
Use the plain badge. In PDFs, videos, email and apps it is never counted, because they don't tell us where it was opened. On a website, the plain badge counts by the site and the label it shows.
Free. The code is open on GitHub.
Yes. Mascots are added on GitHub, and the designer is credited. See how to propose one.
Badges like "Not By AI" say no machine was involved. This is the mirror: a way to say a machine was involved, and that you are not hiding it.
We may remove any place from the public list without notice. It still counts.