Registry Relay
Serves the protected, read-only API over your existing files and tables.
Open Registry Relay →Solution · Protected Registry APIs
Turn existing registries into protected, auditable APIs.
Protected Registry APIs put a safe, read-only doorway in front of a registry you already run, whether it lives in a file, a database, or a legacy system. Approved services get scoped access to agreed fields, and every read is recorded.
Where it fits
Keep the source registry in place. Add the access path around it.
Many institutions already run authoritative registries, but the only way in is a file export, a direct database login, or a one-off API. Protected Registry APIs leave the source where it is and add a governed way to read from it.
- A registry exists, and other services need an approved, official way to read from it.
- A team needs read-only routes without changing the source system.
- Partners need stable routes for real things, like households or suppliers, not raw table names.
- A data-sharing agreement needs its scope, purpose, and audit trail built into the access path.
- A legacy file or database needs a safer front door long before it can be replaced.
How it works
The source stays where it is. The API goes in front.
Existing sources
The registry stays where it is.
CSVXLSXParquetPostgreSQLLegacy API
Registry Relay
Protected read-only surface- sign-in
- scopes
- metadata
- field limits
- audit
Approved services
Services call routes for real things, not database tables.
entity readsmetadata routesallowed countswhat is on offer
What it exposes
Read access to real registry data, shaped for the services allowed to use it.
A protected registry API can return reads by entity, only the agreed fields, metadata, and allowed counts, without opening the underlying database or copying the whole source file.
Reads by real-world entityOnly the agreed fieldsMetadata routesDiscover what is on offerAggregate counts where allowedStandards-shaped views where needed
What it protects
The API is the access path. The source remains authoritative.
- The source system stays in place.
- Callers never receive a database login.
- Routes name real things, not database tables.
- Access is scoped and recorded in the audit trail.
- Sensitive fields can be hidden, narrowed, or withheld.
- Operational settings stay separate from the public description partners read.
How it is built
Two open-source products do the work.
Registry Relay serves the protected read-only API, and Registry Manifest describes the registry so partners know what it offers before they connect.
Registry Manifest
Describes the registry so partners can see what it offers before they integrate.
Open Registry Manifest →Relationship to Evidence Gateway
Safe reads are the foundation for shared evidence.
Protected Registry APIs give trusted systems a safe way to read from a registry. Evidence Gateway builds on that foundation when the caller needs proof of a fact, a yes or no, a redacted answer, or a credential instead of a record.
See Evidence Gateway →Where to start
Start with the registry that already exists.
Registry Relay gives that source a protected read-only API. Registry Manifest makes it easy for partners to see what it offers. Evidence Gateway takes over when the request needs a proof or a credential instead of a record.
For your technical team