> For the complete documentation index, see [llms.txt](https://pulse-capital-2.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pulse-capital-2.gitbook.io/whitepaper/the-ecosystem/capital-farms.md).
# Capital Farms
Capital Farms is a central products of Pulse Capital, designed to offer users enhanced rewards for staking their Native PCAP Liquidity Provider (LP) tokens. This section outlines how Capital Farms works and the benefits for users who stake LP tokens on the platform.
### 1. Staking Native LP Tokens
When users provide liquidity on Pulse Capital, they receive LP tokens, representing their share in the liquidity pool. Instead of merely holding these LP tokens and earning trading fees, users can stake them in Pulse Capital’s Capital Farms for additional rewards.
Enhanced APRs: Staking LP tokens in Capital Farms grants users access to dynamic APRs. This means users earn more by staking their LP tokens in Pulse Capital.
### 2. Earning PCAP Tokens
As a native reward in Pulse Capital, PCAP tokens can be harvested periodically. Users can choose to reinvest these tokens within the Pulse Capital ecosystem or trade them for other assets, maximizing their returns.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://pulse-capital-2.gitbook.io/whitepaper/the-ecosystem/capital-farms.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.