> For the complete documentation index, see [llms.txt](https://spire-docs.gitbook.io/spire/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://spire-docs.gitbook.io/spire/da-builder/getting-started/cost-structure.md).

# Cost Structure

DA Builder applies a **usage-based** pricing model that guarantees efficiency:

* **Execution Gas**: Charged based on your transaction's gas usage. Intrinsic gas costs are shared with network participants, reducing per transaction expense.
* **Blob Gas**: Shared across all transactions in the aggregated blob
  * currently we only support a single blob transaction per batch but we will be adding configurable options for how your blob transactions get processed and what other kinds of transactions they can be batched with
* **Service Fee**: Small fee for aggregation services. The majority of savings are passed back to you, with a portion retained by Spire Labs. *(No Service Fee is charged if no savings are achieved)*

Costs are automatically deducted from your account balance when transactions are included onchain. If your transaction cannot be aggregated, it is submitted directly at cost with no Service Fee. This model guarantees to never increase your cost exposure.

DA Builder ensures savings whenever aggregation is possible.


---

# 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://spire-docs.gitbook.io/spire/da-builder/getting-started/cost-structure.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.