> For the complete documentation index, see [llms.txt](https://docs.unsub.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unsub.org/troubleshooting/how-do-you-calculate-the-open-access-portion-of-the-forecast.md).

# How do you calculate the open access portion of the forecast?

Data we use to calculate the open access portion of your Unsub forecast comes from our other product [OpenAlex](https://docs.openalex.org/). 

The calculation of the open access portion is not based just on whether a journal is open access or not, or how many articles in the journal are open access. It’s based on readership information. Of the articles that people actually visited, what percent of those are open access. To put this in concrete terms, if there’s a journal with 100 articles in it, and people only read 1 paper, it’s essentially a toll access journal. 


---

# 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.unsub.org/troubleshooting/how-do-you-calculate-the-open-access-portion-of-the-forecast.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.