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

# developers

Byzanlink Markets exposes **protocol-level interfaces** that let developers and integrators build on top of vault-based RWAs.

***

## Integration mindset

* **Protocol-first integration**
  * Designed to be embedded into onchain systems and applications
  * Not positioned as a standalone “app only” experience
* **Vaults as primitives**
  * Vaults are the consistent surface for interaction
  * Applications can compose vault interactions into broader workflows

***

## Common build directions (examples)

* **RWA access experiences**
  * Dashboards, discovery, portfolio views
* **Automation & workflows**
  * Scheduled actions, rule-based routing, treasury operations
* **Composable onchain use cases**
  * Integrating vault positions into other onchain logic (where appropriate)

***

## Design principles

* **Non-custodial by design**
  * Assets remain under smart contract or issuer-defined control at all times.
  * Markets does not take custody or assume balance-sheet exposure.
* **Asset-defined behavior**
  * Access mechanics derive from each instrument’s structure (not one-size-fits-all).
* **Vault-based access**
  * Vaults provide a consistent and auditable execution surface.
* **Protocol-first integration**
  * Built for developers and integrators to plug into onchain systems.

***

## Visual: what you integrate with

```mermaid
flowchart TB
  App[Your App / Protocol] --> Vault[Markets Vault Interface]
  Vault --> Instr[Tokenized Instrument Exposure]
```


---

# 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://bzl.gitbook.io/bzl-docs/byzanlink-market/developers.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.