> For the complete documentation index, see [llms.txt](https://fluxflow.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fluxflow.gitbook.io/docs/fluent-connect-prints-integration.md).

# Fluent Connect / Prints Integration

Your reputation is your edge.

We're exploring a reputation layer that changes how rewards work on Flux. The idea is simple: your history should matter.

[Fluent Connect](https://connect.fluent.xyz/signin) will track your real footprint across the Fluent ecosystem like how long you've been here, what you've contributed, and whether you're a human or a bot. The deeper your reputation, the more you stand to earn.

### What could build your reputation:

* **Show up verified** — link your identity through Ethos. Verified humans could earn a multiplier on rewards.
* **Hold the culture** — ecosystem NFTs, community participation, the things that can't be faked.
* **Have a voice** — your X presence and engagement signal you're real and invested.


---

# 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://fluxflow.gitbook.io/docs/fluent-connect-prints-integration.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.