> For the complete documentation index, see [llms.txt](https://docs.northstar.sonicsvm.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.northstar.sonicsvm.org/build.md).

# Build

Practical guides for building on NorthStar — integration, custom economics, production deployment.

This section covers what you need to ship a NorthStar integration. The [Concepts](/concepts.md) section explains the formal model; this is the production-side counterpart.

## In this section

* [Integration Guide](/build/migrate.md) — adopt NorthStar in an existing Solana program. Covers the program-side `delegate_to_portal` hook, client wiring, runtime steps, the Mach AMM worked example, common gotchas, and a testing checklist.
* [Programmable Economics](/build/fees.md) — the full `FeeStructure` surface area. Custom fee tokens, per-instruction schedules, operator revenue capture.

## When to use what

* If you're standing up a new project, start with [Hello World](/getting-started/hello-world.md), then come here for production-grade fees + delegation patterns.
* If you have an existing Solana program, the [Integration Guide](/build/migrate.md) is the entry point.
* If you're building an aggregator or wallet that opens grids on behalf of users, [Programmable Economics](/build/fees.md) covers the revenue-capture model.


---

# 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.northstar.sonicsvm.org/build.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.