> For the complete documentation index, see [llms.txt](https://lpdocs.beqenx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lpdocs.beqenx.com/discord.md).

# LibertyPulse Discord

Most ER:LC servers rely on **too many** separate systems.

That creates duplicate commands, disconnected workflows, and a server experience that feels patched together. Even custom bots can become hard to update, expensive to maintain, and difficult to grow, especially when you rely on a single human being (a bot developer) to do it for you.

### LibertyPulse is different

LibertyPulse is not just a bot.

It is a system for running your community with one foundation. Commands stay centralized. Systems work together. Hosting stays free. Upfront costs stay lower.

### What LibertyPulse solves

* Unbranded and unprofessional ticket systems
* Lack of flexibility
* Inability to customize and grow
* Custom setups that are hard to update or expand
* The lack of access to features you actually want

### Why it matters

LibertyPulse gives your server one product instead of a stack of disconnected ones.

That means you can customize faster, scale with less friction, and automate more of the work that usually stays manual.


---

# 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://lpdocs.beqenx.com/discord.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.
