> For the complete documentation index, see [llms.txt](https://node1.gitbook.io/node1-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://node1.gitbook.io/node1-docs/solana/fast-landing/tip-floor.md).

# Tip floor

## API Info

* **Method:** GET
* **URL:** `/api/v2/tip-floor`
* **Base URL:** `https://node1.me`
* **Auth:** Not required

## Request Example

```bash
curl https://node1.me/api/v2/tip-floor
```

## Success

```json
{
  "tip": 0.0
}
```

## Response Description

* **tip:** The recommended tip amount (in SOL), calculated based on current network conditions.
* This value serves as a guideline for setting an appropriate tip to achieve better processing priority.
* This value automatically adjusts in response to network congestion and demand.

## Usage Notes

* This endpoint requires no authentication.
* The return value is dynamically calculated and can be queried periodically to adapt to the latest network conditions.
* It is recommended to use this in conjunction with the "Transaction Optimization Guide" to comprehensively configure your tipping strategy.


---

# 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://node1.gitbook.io/node1-docs/solana/fast-landing/tip-floor.md?ask=<question>&goal=<endgoal>
```

`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.