> 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/earn-by-sharing/find-products-to-promote.md).

# Find products to promote

How to find products worth sharing: the commission is shown up front, and fit beats percentage.

Here is how to find products worth sharing with your audience.

## Steps

1. Open [Explore](https://lid.pro/en/discovery) on lid.pro, where every listed product appears. Filter by type or topic.
2. Look for products that offer a commission. The percentage is shown on the product page before you share, anywhere from 1% to 50%.
3. Ask yourself: would I recommend this to a friend for free?
4. Ask the second question: does my audience actually want this?
5. Read the product page like a buyer. Clear description, clear price, clear deliverable.

{% hint style="info" %}
A good fit converts better than a big percentage. A product your audience wants at 15% beats a product they ignore at 50%.
{% endhint %}

## Common questions

<details>

<summary>What commission can I expect?</summary>

The seller sets it, between 1% and 50%. The number is always visible before you share.

</details>

<details>

<summary>Do I need permission from the seller?</summary>

No. If a product shows a commission, it is open to everyone.

</details>

<details>

<summary>How many products should I share?</summary>

Start with one. Add more once you see what your audience responds to.

</details>

When you find something worth sharing, this is where to start: [lid.pro](https://lid.pro)


---

# 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/earn-by-sharing/find-products-to-promote.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.