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

# Technical Architecture

<figure><img src="https://1087592013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGcspr3cyfJvCi6NzTi8U%2Fuploads%2FupMaNqNcrqX4qaRspG3O%2FTechnical%20Architecture%20NB.png?alt=media&amp;token=1891a71a-66eb-4b04-ad59-a5013d9f1bd3" alt=""><figcaption></figcaption></figure>

Linkary is composed of cooperating identity, public-profile, analytics, onchain, and monetization layers.

```
                         +----------------------+
                         |   Public Experience  |
                         | Profiles / Bids / SEO|
                         +----------+-----------+
                                    |
                                    v
+------------------+     +----------+-----------+     +------------------+
| Identity & Auth  | --> | Linkary Application  | <-- | Social / Project |
| Canonical User   |     |   & API Services     |     | Integrations     |
+------------------+     +----------+-----------+     +------------------+
                                    |
                    +---------------+----------------+
                    |                                |
                    v                                v
          +---------+----------+           +---------+----------+
          | Analytics /       |           | Wallet / Onchain   |
          | Attribution       |           | Verification       |
          +---------+----------+           +---------+----------+
                    |                                |
                    +---------------+----------------+
                                    |
                                    v
                         +----------+-----------+
                         | Monetization /       |
                         | Auction State        |
                         +----------------------+
```

## Design principles

**Canonical identity.** External providers attach to a canonical Linkary account.

**Verifiable settlement.** Auction payment state is verified server-side rather than accepted from a client assertion.

**Public/private separation.** Public profiles expose intended public information while sensitive account and wallet controls remain authenticated.

**Real-data marketplace.** Production marketplace surfaces should use actual eligible profiles, views, and bids.

**Cost-aware processing.** Queries and processing should avoid unnecessary full-table scans and repeated expensive reads.


---

# 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://linkary.gitbook.io/linkary-docs/technical-architecture.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.