> 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/welcome-to-linkary/how-linkary-works.md).

# How Linkary Works

<figure><img src="https://1087592013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGcspr3cyfJvCi6NzTi8U%2Fuploads%2FewpOd3cRm63fteff4oar%2FHow%20Linkary%20Works.png?alt=media&amp;token=941b03a3-2942-4a2e-8a1e-4597e7a21a0a" alt=""><figcaption></figcaption></figure>

Linkary combines a public presentation layer with identity, attribution, wallet and monetization services.

```
User / Project
      |
      v
Linkary Account
      |
      +--> Public Profile
      +--> Social & Project Links
      +--> NFT Showcase
      +--> Campaign Signals
      +--> Linkary Wallet
      |
      v
Analytics & Attribution
      |
      v
Reputation / Monetization Surfaces
```

{% stepper %}
{% step %}

## Establish identity

A user signs in and establishes a canonical Linkary account. Supported external providers are associated with that account rather than intentionally creating separate users.
{% endstep %}

{% step %}

## Build the public profile

The user can publish a profile containing public information, links, projects and supported digital-asset showcases.
{% endstep %}

{% step %}

## Generate measurable activity

Public-profile visits, supported campaign interactions and onchain signals can contribute to analytics and attribution where enabled.
{% endstep %}

{% step %}

## Monetize eligible inventory

Eligible profile owners can make their public-profile header available through Linkary's auction system. Advertisers bid for the placement. Bidding does not transfer funds. The winner settles afterward.
{% endstep %}
{% endstepper %}


---

# 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/welcome-to-linkary/how-linkary-works.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.