> For the complete documentation index, see [llms.txt](https://ninjapay.gitbook.io/ninjapay-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ninjapay.gitbook.io/ninjapay-api-docs/how-to/api-reference-upi/plugins/paywalls.md).

# Paywalls

A Ninjapay paywall is a digital barrier that restricts access to online content, requiring users to pay fee. It allows publishers to monetize their content by providing exclusive access to paying users, enhancing revenue streams for digital content providers.

Use-cases:

* **News Websites**: Charge readers for access to premium articles and exclusive content, generating revenue for quality journalism.
* **Online Magazines**: Offer subscribers special editions and archived content, monetizing digital magazines through subscriptions.
* **Educational Platforms**: Restrict access to courses and tutorials, charging users for valuable knowledge and certification programs.
* **Streaming Services**: Provide premium content like ad-free experiences and exclusive shows to paying subscribers.
* **Research and Academic Journals**: Offer access to research papers and scholarly articles to subscribers or one-time purchasers.

<figure><img src="/files/0O6rVKaPRTFoV92MKwES" alt=""><figcaption><p>Ninja lightning voucher</p></figcaption></figure>


---

# 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://ninjapay.gitbook.io/ninjapay-api-docs/how-to/api-reference-upi/plugins/paywalls.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.