Registries
Who runs PRE-GEN today. Registries and providers are listed so they can find each other and give consistent answers about the same people and works.
Registries
A registry holds subjects, issues licences and signs decisions.
| Name | Role | Codes | API | Status | Since |
|---|---|---|---|---|---|
| PRAMPTA | Registry operator, origin issuer | PG-… (bare codes) | https://api2.prampta.com | Production | 2026 |
Providers
AI systems that ask a listed registry before generating.
| Name | Registry | Status |
|---|---|---|
| None yet. A provider appears here once it completes a production check and receipt with a listed registry. | ||
Getting listed
Registries open an issue in the specification repository with:
- a public API with
/v1/verify/,/v1/subjects/indexand a rotation-aware key set at/keys; - a passing run of the published test vectors;
- a contact for rights holders and a contact for security reports.
Providers are listed by the registry they integrate with, after a production decision and matching receipt.
Working together
Proposed, not yet part of the specification. Discussed in the open before anything changes on the wire.
- One code, one issuer. A PG code belongs to exactly one registry. A bare
PG-…code always means the origin registry; other registries get their own prefix (PG-<ISSUER>-…, format under discussion), so codes never collide. - Discovery. Each registry publishes the same machine-readable description of its endpoints and keys, so one provider integration can reach every listed registry.
- A no is shared. An opt-out or a protection for a minor at one registry should be honoured by every registry holding the same person.
- Disputes. When two registries claim the same person or work, neither issues new licences for it until the claim is resolved.