> For the complete documentation index, see [llms.txt](https://docs.vena.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vena.finance/points-and-incentives/overview.md).

# Overview

Four distinct reward streams accrue to users on Vena, each with its own earning surface and claim path.

| Stream                | What it is                                   | Earned by                                    | What it affects                            | Claimable?                   |
| --------------------- | -------------------------------------------- | -------------------------------------------- | ------------------------------------------ | ---------------------------- |
| **Vena Points**       | Vena's internal points system                | Using Vena (supply, borrow, duration)        | Convert into $VENA tokens at $VENA TGE     | Yes, via $VENA conversion    |
| **Prints**            | Fluent's network-wide reputation primitive   | Activity across the Fluent ecosystem         | Your Vena borrow / supply terms            | No — reputation, not a token |
| **$BLEND incentives** | Fluent's native token distributed as rewards | Supplying / borrowing eligible assets        | Boosts your effective APY                  | Yes, via Merkl               |
| **Partner points**    | Third-party partner programs                 | Using Vena markets integrated with a partner | Partner-side loyalty / airdrop eligibility | Varies per partner           |

These stack on a single position without interfering with each other. A user supplying an eligible asset can earn the base supply APY, $BLEND incentives, and Vena Points simultaneously; if the market is integrated with a partner program, partner points accrue on top. A borrower's rate is separately adjusted by their Prints reputation.

The four streams do different things, earn in different ways, and claim through different surfaces. The sections below introduce each in short form; each has its own page for detail.

## Vena Points

Vena's own internal points system. Earned by using Vena — supplying, borrowing, and position duration all contribute. Vena Points convert into $VENA tokens at $VENA TGE.

See [Earning Vena Points](/points-and-incentives/earning-vena-points.md).

## Prints

Fluent's network-wide reputation primitive. Earned by activity across the Fluent ecosystem, not just on Vena. Prints are not tokens and are not claimable — they're a portable signal that protocols on Fluent can read. Vena reads Prints to adjust borrower rates.

Strong Prints change the rate a borrower pays on Vena. Vena Points are a separate points balance that converts into $VENA. See [Why Vena](/welcome/why-vena.md#prints-vs-vena-points) for the contrast in detail.

For the primitive itself, see [Fluent Connect](https://connect.fluent.xyz/signin) — the Prints platform on Fluent.

## $BLEND incentives

$BLEND is Fluent's native token, distributed to Vena users as rewards on eligible markets. Rewards accrue as an effective APY boost on top of the base supply or borrow rate, and are claimed via Merkl. One restriction worth knowing: same-asset supply / borrow positions in the same wallet net out and don't accrue.

See [$BLEND incentives](/points-and-incentives/blend-incentives.md).

## Partner points

Third-party programs that accrue to users whose Vena position interacts with a partner protocol's markets or strategies. Each partner sets its own earning rules, balance view, and claim surface; points accrue independently of Vena Points and $BLEND and are redeemed on the partner's own platform.

For example, supplying USDnr on Vena can earn points from the stablecoin issuer's own program, and a USDC deposit routed through a partner yield vault into a Vena market can earn the partner's points on top of Vena's base APY and $BLEND boost.

The list of integrated partner programs grows as integrations land and is reflected on each partner's own site.


---

# 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.vena.finance/points-and-incentives/overview.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.