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

# Developer overview

Souless is a TypeScript/Solidity monorepo. The contracts are canonical for settlement and custody; the API/indexer turns chain events into product data; the web app prepares user-signed actions.

```
Web or agent client ──→ Souless API ──→ Indexed market data
         │                                    ▲
         ▼                                    │
User-authorized wallet ──→ Souless contracts ─┤
                                  │            │
                                  ▼            │
                             Uniswap V3 ───────┘
```

## Integration rules

* Read addresses from the published network reference; do not hard-code an address from prose.
* Bind writes to chain ID, contract, nonce/deadline, limits, and the connected wallet.
* Treat API quotes as expiring preparations, not settlement guarantees.
* Confirm submitted transactions independently from finalized chain events.
* Use integers for token atomic units and basis points; never use floating-point arithmetic for settlement.
* Fail closed when network, address, ABI, or policy version is missing.

REST API, webhooks, supported SDKs, MCP, agent skills, authentication tiers, and production rate limits are **UNDER DEVELOPMENT**. Current application routes are not a stability promise until a versioned public API is released.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.souless.fun/developers/overview.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 `automate deployments from our CI pipeline` 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.