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

# Welcome to WLFI Docs

Welcome to the **World Liberty Financial documentation**, the official source for understanding, building with, and navigating the products, tools, and governance of World Liberty Financial.

World Liberty Financial bridges traditional financial infrastructure with blockchain innovation, creating accessible, transparent, and scalable solutions for a new era of digital finance. This documentation is intended for developers, integrators, researchers, and community members seeking to understand the World Liberty Financial ecosystem.

***

## Our mission

World Liberty Financial is focused on simplifying and expanding access to financial services by combining the reliability of legacy finance with the openness of decentralized systems. We build on-chain financial products designed to support users, institutions, and partners while advancing the next generation of digital financial infrastructure.

Our core objectives include:

* Bridging traditional finance and decentralized finance
* Supporting reliable and scalable stablecoin infrastructure
* Enabling accessible and efficient capital markets
* Simplifying adoption of decentralized financial systems

***

## What you will find here

This documentation is organized to provide a comprehensive overview of the World Liberty Financial ecosystem:

* **Products**\
  Documentation for World Liberty Financial products and tools, including **USD1**, our flagship stablecoin
* **Ecosystem Overview**\
  Platform architecture, system design, and integrations
* **Governance and Tokenomics**\
  Governance mechanisms and the WLFI token
* **Guides and Use Cases**\
  Explanatory guides and practical usage examples
* **Policies and Disclosures**\
  Legal, compliance, security, and risk-related documentation

***

## Quick links

* **Website:** [https://www.worldlibertyfinancial.com](https://www.worldlibertyfinancial.com/)
* **X (Twitter):** <https://x.com/WorldLibertyFi>
* **LinkedIn:** <https://www.linkedin.com/company/worldlibertyfi/>
* **Telegram:** <https://t.me/defiant1s>
* **Medium:** <https://medium.com/@wlfi>
* YouTube: <https://www.youtube.com/@worldlibertyfinancial>

***

## Important disclosures

This documentation may reference evolving products, protocols, and governance mechanisms. Features, terms, and availability may change over time. WLFI does not provide investment, legal, regulatory, tax, or compliance advice, and you should consult qualified professionals regarding your specific circumstances


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.worldlibertyfinancial.com/get-started/readme.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 `build a script that syncs our docs to a CMS` 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.
