> For the complete documentation index, see [llms.txt](https://about.oa.report/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://about.oa.report/docs/sources.md).

# Data sources

OA.reports builds on open data like OpenAlex, Crossref, and ShareYourPaper. In our premium plans, we can ingest the institution's internal data, and collect our own to help power more insights and strategies.

## Open scholarly metadata sources

Thanks to all these services for sharing open data we can build off:

* [Crossref](https://crossref.org/)
* [Unpaywall](https://unpaywall.org/)
* [OpenAlex](https://openalex.org) (and [their sources](https://docs.openalex.org/additional-help/faq#where-does-your-data-come-from))
* [Shareyourpaper.org Permissions](https://shareyourpaper.org/permissions)
* [DOAJ](https://doaj.org/)
* [ORCID](https://orcid.org/)
* [Europe PMC](https://europepmc.org/)
* [Pubmed](https://www.ncbi.nlm.nih.gov/pmc/)
* [Pubmed Central](https://pubmed.ncbi.nlm.nih.gov/)
* [ROR (Research Organization Registry)](https://ror.org/)
* [Datacite](https://datacite.org/)

## Institution's data

We clean & ingest data from a wide variety of institution-specific sources, including:

* Grant reporting systems
* Grant databases
* Compliance tracking systems
* Financial systems
* APC invoices
* Publisher payment dashboards

## Data we collect

We collect data that isn't readily available elsewhere, including:

* Grant IDs
* Acknowledgement sections
* Corresponding author's email addresses
* Data availability statements
* Data & code licences
* Submitted/accepted dates
* Article type (e.g review, correspondence, etc)

## Integrations

We do direct integrations with some services when they're not well included in [open scholarly metadata sources](#open-scholarly-metadata-sources), including:

* Figshare
* OA Switchboard
* Dataseer
* Github
* OSF
* Dataverse
* Bing
* bioRxiv & medRxiv


---

# 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://about.oa.report/docs/sources.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.