> 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/data-and-integrations.md).

# Data and Integrations

Linkary combines application data with selected external and onchain sources.

Core state includes users, public profiles, projects, campaign information, auction records, bids, payment-verification state, and delivery metadata.

Base is used for the current auction settlement flow. Wallet balances can be retrieved live rather than treated as permanent database balances.

Social and attribution integrations can evolve independently from the canonical Linkary identity. Additional chain support should likewise be treated as an integration decision rather than a reason to replace the account model.

<figure><img src="https://1087592013-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGcspr3cyfJvCi6NzTi8U%2Fuploads%2Fu6w8W68O3yQ13mWkaW0e%2FData%20and%20Integrations.png?alt=media&amp;token=3dada1f8-7915-444b-8f8f-db64799c2edd" alt=""><figcaption></figcaption></figure>


---

# 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/data-and-integrations.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.