> For the complete documentation index, see [llms.txt](https://open-data-charter.gitbook.io/open-up-guide-using-open-data-to-combat-corruption/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-data-charter.gitbook.io/open-up-guide-using-open-data-to-combat-corruption/summary/whats-in-the-report.md).

# What’s in the report

This Open Up Guide report is intended to be part of a growing body of work using open data to fight corruption. It includes:

* Use cases and methodologies. A series of case studies highlight existing and future approaches to the use of open data.<br>
* [30 priority datasets](https://airtable.com/shrHY9KFJ5bircwvx/tblOY2aw1hYUuJze9) and the key attributes needed so that they can talk to each other. To address corruption networks it is particularly important that connections can be established and followed across data sets, national borders and different sectors.<br>
* Data standards. Standards describe what should be published, and the technical details of how it should be made available. The report includes some of the relevant standards for anti-corruption work, and highlights the areas where there are currently no standards.


---

# 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://open-data-charter.gitbook.io/open-up-guide-using-open-data-to-combat-corruption/summary/whats-in-the-report.md?ask=<question>&goal=<endgoal>
```

`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.