Product · Evidence Gateway
The registry owner defines one question, who may ask it, for what purpose, and which answer may be returned. Evidence Gateway authorizes the request before source access, makes one fixed lookup, and returns a signed minimum-disclosure assertion. The source record stays with the authority.
Evidence Gateway is a stateless assertion service, not an eligibility or case-management engine.
When to use Evidence Gateway
Start with a question that a service needs answered, such as whether a business is registered or a household is enrolled. The service receives the signed answer and verifies it against independently configured trust and request expectations.
How it works
The registry owner defines the question, purpose, authorized service, and how the answer is represented. Evidence Gateway applies that reviewed definition to every request.
How an evidence request is handled
The registry owner defines the question, the service that may ask it, the purpose, and the possible response.
Evidence Gateway authenticates the service and authorizes the complete predefined request before acquiring source credentials or reading data.
Evidence Gateway makes one fixed, bounded source request and validates the response. It does not browse candidates or copy the source record.
Evidence Gateway derives only the declared value, signs the assertion, records the disclosure, and then releases the response.
One stateless signed assertion containing the approved answer.
Signed minimum-disclosure assertion
The assertion carries its purpose, audience, validity, and an opaque subject binding. The relying service verifies it before use.
Two durable audit gates Authorized access is recorded before the source read. The released disclosure is recorded after signing and before the response leaves.
Define the evidence
The registry owner, service team, and policy owner should agree what the answer means, who may receive it, and how long it remains useful.
Write the question in service language. Define whether the answer is a yes or no, a status, a date, or another small piece of evidence.
Name the public or partner service, the purpose it may declare, and the authority it must present before any source access.
Agree how recent the source observation must be and how long the signed assertion may be accepted.
Keep the decision boundary clear
A licensing portal may ask whether a business registration is active. Evidence Gateway can return that signed fact, but it does not decide eligibility, approve a permit, rank a case, or certify that the source itself is correct. Those responsibilities remain with the authoritative institution and the relying service.
See more public-service examples →When a service needs data
Evidence Gateway provides one signed answer. Registry Relay provides selected data from an existing registry through a protected, read-only API. Evidence Gateway may also use a Relay API as its one fixed source without merging the two products’ authorization models.
Open-source components
The technical documentation explains how each component is configured and deployed.
Authenticates and authorizes one predefined request, makes one fixed source call, and returns a signed minimum-disclosure assertion.
Can expose selected registry data or act as Evidence's fixed, protected source while retaining its own authorization rules.
Publishes portable registry metadata and can describe the evidence and access surfaces an institution offers.
For your technical team