> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/registry/registry/features/standards-compliance.md).

# Standards Compliance

The Base Registry is built to be compatible with widely adopted interoperability standards for identity, data exchange, and registry events. The platform supports JSON Schema for structural validation and JSON-LD for semantic meaning, making registry payloads machine-interpretable across systems. The registry can be integrated with consent standards such as the Kantara Consent Receipt and event exchange standards such as SPDci, enabling it to operate within large-scale governmental identity and social protection ecosystems.

Partner search follows the same split. The DCI adapter speaks DCI request and response envelopes today. The search engine under it does not, so another registry-search profile can be added without a second query implementation. See [Partner Register Search](/products/registry/registry/features/partner-register-search.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openg2p.org/products/registry/registry/features/standards-compliance.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.