# About the DPI Wiki

In a crowded technology innovation landscape and a sometimes polarised geopolitical climate, Digital Public Infrastructure (DPI) has emerged as an unusual point of convergence across countries. It is now widely recognised as a powerful strategy to drive inclusive and sustainable economic growth.

Through the DPI Wiki, we have attempted to distil 15 years of practical implementation experience and insights across countries, cutting across some of the key areas that make up what we call the “DPI Approach”. It is designed to be a living resource, constantly updated with what is new and what is important. 

We’ve tried to simplify it to the absolute minimum of what you need to know to get started in the execution of an inclusive, interoperable, and high-scale DPI in your country: across agriculture, finance, health, education, skilling, ecommerce, and beyond. 

<mark style="background-color:purple;">To the builders and practitioners in countries working tirelessly to solve large-scale societal problems, this wiki is dedicated to you.</mark> &#x20;

We hope it helps bring you closer to your implementation goals.&#x20;

Send us your dashboards so we can celebrate with you!

With warm wishes,&#x20;

Kamya Chandra | Vijay Vujjini&#x20;

Anusree Jayakrishnan | Tanushka Vaid

Ysaias Alvarez | Antony Muriithi

**Citation guidelines:**

**Centre for DPI. (2024).&#x20;*****\[Title of the Article]***\*\*. DPI Wiki. Retrieved from <https://docs.cdpi.dev/**&#x20>;

For example:

**Centre for DPI. (2024).&#x20;*****Understanding DPI*****. DPI Wiki. Retrieved from <https://docs.cdpi.dev/understanding-dpi>**

<br>


---

# Agent Instructions: 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:

```
GET https://docs.cdpi.dev/the-dpi-wiki/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.