> For the complete documentation index, see [llms.txt](https://learn.fueled.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.fueled.io/readme.md).
# Introducing Fueled
Fueled is a purpose-built 1st-party Attribution Suite, designed specifically for eCommerce.
With Fueled, all of your first-party and zero-party customer data flows between your sales, marketing, and BI tools — helping you understand and personalize customer experiences, and increase return on your marketing spend.
Visualization of how events flow through Fueled, from eCommerce technologies to various “destination” technologies.
## Getting Started
Please use this knowledge base website to learn more about Fueled and, more generally, customer data platform/stack strategies.
If you want to skip the line, just [fill out our sign-up form](https://fueled.io/sign-up), and we will get back to you right away about getting started with Fueled.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://learn.fueled.io/readme.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
