> For the complete documentation index, see [llms.txt](https://participanthelp.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://participanthelp.dscout.com/getting-paid/frequently-asked-questions.md).
# Frequently asked questions
Quick answers to common payment questions.
Okay seriously, what's the catch?
There's no catch.
If you're invited to a study, you're eligible to be paid.
Follow the study directions and complete every required activity on time.
The project team reviews your entries before payment starts.
Once approved, we message you with the exact reward date.
When we send the reward, PayPal emails you.
Dscout also sends a push notification.
Do I get paid for applications?
Applications to studies are unpaid.
Applications help determine whether you're a good fit for a study.
Think of them like an audition.
We do show the reward amount before you start.
You can find it on the study card and study details page.
**Pro tip:** Read the study overview before you apply.
It helps you decide whether the study is a fit.
If it is not, tap **Not Interested**.
You can also review [Best practices for applying to studies](/getting-started/dscout-overview/best-practices-for-applying-to-studies.md).
How much do studies pay?
Most studies offer a cash reward.
You receive it when you meet the requirements and finish all activities.
Most payouts range from `$25` to `$150`.
Some studies pay more.
Some pay less.
The final amount depends on the study's time and effort.
To check a study's reward in the app:
1. Open the **Studies** tab.
2. Find the study.
3. Check the **Reward amount** on the study card.
4. If needed, open the study and read the **Study overview**.
If you do not see a reward total, the study may use a different payment setup.
See [Receiving external payments](/getting-paid/payment-basics/receiving-external-payments.md).
---
# 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://participanthelp.dscout.com/getting-paid/frequently-asked-questions.md?ask=&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.