External adoption
Adoption registry
Third parties that have built on Harpd data, verified by a human before listing. This is the one adoption count Harpd cannot inflate: every entry links to a real site usingreal Harpd data.
Quick answer
Who has adopted Harpd data?
No adoptions are verified yet — the registry starts empty by design, so it can never show a fabricated entry. Register yours at /developers/adopt/ and it appears here once confirmed. Harpd publishes 1,122 products as open CC BY 4.0 datasets; the registry tracks who genuinely reuses them.
- Verified adoptions
- 0
- Listed
- None yet
- Source
- Human-verified
- License
- CC BY 4.0
Data source: Harpd adoption registryRegister adoptionAdoption metrics
Verified adopters
No adoptions verified yet.
The registry is populated only after a maintainer verifies a self-reported adoption, so it begins empty rather than with invented entries. Built something on Harpd? Register it and we'll list it once confirmed.
How an entry gets here
- A developer posts a self-report at /developers/adopt/ (or via
/api/adoption-event). That logs an event only — it never appears here. - A maintainer visits the submitted site, confirms it genuinely renders or serves Harpd data, and attributes Harpd.
- If legitimate, the entry is added to
src/data/adoptions.jsonand appears on this page on the next deploy.
This verify-then-list rule is why the registry is trustworthy: it can only ever contain real, checked adoptions.