> For the complete documentation index, see [llms.txt](https://docs.lid.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lid.pro/sell-on-lid/bounties.md).

# Challenges

Run a challenge with a prize: post it, fund the pool, choose who gets each prize, and each prize holder claims their prize. Called bounties in the API.

A challenge is a competition with a prize. You post it, people compete, you choose who gets each prize, and each prize holder claims their prize.

{% hint style="info" %}
Challenges were called Bounties until August 2026. Same feature, clearer name. Older links still work.
{% endhint %}

![A finished challenge on lid.pro: a $100.00 prize pool, $100.00 assigned and $100.00 paid out, split into three places of $50.00, $30.00 and $20.00.](https://1004546140-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQKVT6WDKWT4P06WmWa57%2Fuploads%2FnFbEiEZl8yLrK6VX5MS9%2Flid-challenge-desktop-2026-10-15.png?alt=media)

## Steps

1. Open **My challenges** in your [dashboard](https://lid.pro/dashboard) and click **New challenge**.
2. Describe the challenge and how you will judge it, in plain language.
3. Set the prize and how it splits across places.
4. Set a deadline, or leave it open.
5. Fund it and publish.

The prize money is set aside safely the moment you publish. Participants can see it is there before they start working, so they trust the challenge.

You can also ask entrants to verify their identity, add your own entry questions, or show the challenge only on your own site.

## Assigning the prizes

Submissions arrive in your dashboard. You choose who gets each prize. The moment you approve, each prize is assigned, with a public record anyone can check, and its holder claims it from their own dashboard.

## FAQ

<details>

<summary>Is there a fee?</summary>

Yes, the flat 3%, and you cover it, so each prize holder receives the full prize. To give $100 in prizes, you fund $103.09; 3% of that is the fee.

</details>

<details>

<summary>When do prize holders get their money?</summary>

Their share is locked in the moment you approve. They claim it from their dashboard whenever they want, and nobody can take it from them in between, including you.

</details>

<details>

<summary>Can I get the prize money back?</summary>

Not once anyone has entered. The prize money only leaves toward the people you assign it to. It comes back to you only if nobody entered and the deadline passed.

</details>

<details>

<summary>Can I delete a challenge?</summary>

Once it has money in the pool or any entries, you can archive it, not delete it. An archived challenge leaves the listings, and its link keeps working.

</details>

<details>

<summary>What is a challenge good for?</summary>

Design, content, code, translations, or rewarding your community for actions that matter to you.

</details>

Post your first challenge at [lid.pro](https://lid.pro). That is the link if you want to sell.


---

# 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://docs.lid.pro/sell-on-lid/bounties.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.
