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

# Overview

<figure><img src="/files/eaEalZUj5bjgRL4x4G9k" alt=""><figcaption><p>Two-Way Bridge High Level Architecture</p></figcaption></figure>

The Bridge is made up of two main elements - the API and the Core.

The API is a Web2 stack with a HTTPS API to allow integrations to registries, as well as a secure, non-internet facing compute layer for processing sensitive operations.

The Bridge Core references the smart contracts that make up the on-chain logic and data.

## Custody Model

Thallo uses a custody model to ensure that each and every tokenized credit is backed by exactly one credit of the same project/vintage. We do not employ any over or under collateralization - it is 1:1. This ensures the tokenized credits have the same attributes and market value as their analogue counterparts, whilst still enjoying all the benefits of being fully traceable, transparent and immutable on the blockchain.


---

# 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.thallo.io/architecture/overview.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.