> For the complete documentation index, see [llms.txt](https://heroes-build.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://heroes-build.gitbook.io/docs/tutorials/funding-a-bounty/accepting-claim-proposals.md).

# Accepting Claim Proposals

[![Image description](https://res.cloudinary.com/practicaldev/image/fetch/s--rIIDgUrB--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/kte6ap60lzjz7i2jejz0.png)](https://res.cloudinary.com/practicaldev/image/fetch/s--rIIDgUrB--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/kte6ap60lzjz7i2jejz0.png)

You'll get an email notification when Hunters have applied to claim your bounty. When you're back in HEROES head to "your bounties." 

[![Image description](https://res.cloudinary.com/practicaldev/image/fetch/s--GtYUsxGO--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/8res0rwmbrx7ce9owz4e.png)](https://res.cloudinary.com/practicaldev/image/fetch/s--GtYUsxGO--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_800/https://dev-to-uploads.s3.amazonaws.com/uploads/articles/8res0rwmbrx7ce9owz4e.png)

After you click into the relevant bounty head to the Applicants tab so you can approve or reject claim proposals. 

Accepting the claim will start the time commitment countdown (the hunter is required to provide an estimate if you don't specify any time constraints).


---

# 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://heroes-build.gitbook.io/docs/tutorials/funding-a-bounty/accepting-claim-proposals.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.