> For the complete documentation index, see [llms.txt](https://docs.cdpi.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cdpi.dev/technical-notes/digital-ids-and-electronic-registries/digital-id/capabilities-on-id-system.md).
# Capabilities on ID system
Building a use cases layer on top of any foundational / functional ID system is crucial for unlocking service delivery. An ID system should be considered infrastructure that provides citizens with seamless access to services.
An ID system is only as powerful as the use cases it can unlock. This is also how countries can encourage enrollment and ensure that their ID system is “sticky”.
The layers built on an identity system, as outlined below, can make an existing ID system operate as digital public infrastructure in an economy, thereby enhancing both enrollment rates and overall system utilization.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.cdpi.dev/technical-notes/digital-ids-and-electronic-registries/digital-id/capabilities-on-id-system.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.