Why integrate Human Origin
AI detectors guess from the finished work and are often wrong. Human Origin records that a person examined how the work was made, and keeps that record public and up to date.
A status you can trust
Each reviewed creator has a numbered public record. If the rules are broken, the status turns to revoked everywhere, including on your platform.
Proof tied to the exact file
Certified works are identified by the SHA-256 fingerprint of their original file. A badge reused on another image or text simply doesn’t match.
Nothing to store, nothing to upload
Fingerprints are computed in the browser. You never handle creators’ source files, and the API only returns what is already public.
Use cases
Art and photo competitions
- The problem
- Your rules ban AI, but the jury can’t check every entry.
- With the API
- At submission, the entry form fingerprints the file in the participant’s browser and asks the API whether it is a certified work.
- The result
- The jury sees “certified work, process reviewed” with a link to the proof, without ever receiving source files.
Freelance and creator platforms
- The problem
- Clients want human creators, and badges on profiles are easy to copy.
- With the API
- Creators add their Human Origin number to their profile; your platform checks it through the API and compares the declared website and accounts.
- The result
- Your own “verified human creator” mark, which turns red automatically if the badge is revoked.
Publishers and literary agents
- The problem
- More and more submissions are suspected of being generated, and detectors are not reliable.
- With the API
- Authors give their number in their cover letter; you check it, and compare the manuscript’s fingerprint with their certified works.
- The result
- Stronger evidence than any detector score, without asking authors for their drafts.
Galleries and art marketplaces
- The problem
- Buyers are wary of generated visuals sold as handmade.
- With the API
- Each product page queries the API with the artist’s number and, for digital editions, the fingerprint of the original file.
- The result
- A status that is always current, shown on the listing and linked to the proof.
For juries: no integration needed
No developer? Your jury can check entries today with our free Jury check tool.
- Ask for originals and numbers. In your rules, ask participants for the original file of each entry and, if they have one, their Human Origin number.
- Drop the files into Jury check. Each file is fingerprinted in the juror’s browser and compared with all certified works. Nothing is uploaded.
- Paste the numbers, with each participant’s website if you like, to see who is a reviewed creator and whether the website matches.
- Download the results as a spreadsheet (CSV) and share them with the rest of the jury. Each line links to the public proof.
Integrate in an afternoon
- Ask creators for their number. A simple field such as “Human Origin ID”, for example
HO-2026-0012. - Check it at display time with
GET /api/v1/creators/{id}, and compare the website and accounts it returns with the profile. - Check files when it matters: compute the SHA-256 in the browser with our open-source library, then call
GET /api/v1/works?sha256=…. - Show the status and link to the proof: always link to the verification page wherever you show a reviewed status.
// Show a "verified human creator" mark only when the record is valid
const res = await fetch('https://human-origin-label.lochness-paris.com/api/v1/creators/HO-2026-0012');
if (res.ok) {
const { creator } = await res.json();
const valid = creator.status === 'reviewed' && !creator.demo;
// display your mark if valid, linked to creator.url
}
Open-source tools, JSON Schemas and examples: GitHub repository · Full rules: specification.
Integrating responsibly
Do
- Query the status when you display it, so revocations show up.
- Link to the creator’s verification page.
- Compute fingerprints on the user’s device.
- Explain that a match covers the exact original file.
Don’t
- Show a self-declared or demo record as reviewed.
- Present the label as proof that no AI was ever used.
- Upload users’ files to check them.
- Alter the Human Origin badges.
Integrations that follow these rules are conforming integrations, as defined in Section 13 of the specification.
Running a competition or a platform?
During the pilot, we can help you set up the integration and review your first creators. Tell us about your project.