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

# Welcome to LOGIA

**Logia is a privacy layer built on top of the x402 protocol enabling private payments, private transfers, and private on-chain actions without needing a backend or trusting a third party.**

Today, every payment you make online is traceable. Wallets reveal your identity, transactions expose your habits, and apps can map your entire financial history. Logia fixes this by introducing **client-side zero-knowledge privacy** to the x402 payment standard.

With Logia, apps can send and receive payments privately, agents can operate without exposing the user, and developers can integrate privacy without knowing cryptography.

Logia turns x402 into what it always should have been:\
**an internet-native payment protocol with built-in privacy.**


---

# 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://docs.logiaterminal.com/readme.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.