> For the complete documentation index, see [llms.txt](https://docs.quantaria.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quantaria.xyz/guides/integration-guide.md).

# Integration Guide

This guide covers using Quantaria models in your own applications and workflows.

## Current access

Today, Hilbert-1 Nano and Base are used through the [Quantaria Console](https://github.com/bhavy2908/dataai_docs/tree/main/overview/quantaria-console.md) at [console.quantaria.xyz](https://console.quantaria.xyz). See [Getting Started](/guides/getting-started.md).

## Programmatic access

> **TODO (Quantaria team):** document programmatic access if it is available: API endpoint and authentication, request and response formats, model identifiers, error handling and usage limits. Nothing has been published here, so none of these details are specified in these docs.

## Bond library

Bond is the PyTorch library behind every Quantaria model, covering tensor-train and MPO layers, rank-adaptive training, canonical gauging and fused contraction kernels. It is planned for open-source release.

> **TODO (Quantaria team):** add installation instructions, repository link, license and a usage example when Bond is released.

## Questions and collaboration

For integration questions, email <hello@quantaria.xyz>.


---

# 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.quantaria.xyz/guides/integration-guide.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.