> For the complete documentation index, see [llms.txt](https://docs.ariaagi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ariaagi.com/getting-started/home.md).

# Home

**Ship the right thing.**

ARIA is an AI workspace for founders who want evidence before execution. You buy credits, run the pipeline, and ARIA handles research, validation, strategy, deploy, and MVP generation on platform infrastructure, no API keys to wire up.

{% hint style="info" %}
This handbook describes **ARIA Basic** the launch experience every operator sees. There is no separate Pro tier and no bring-your-own-keys setup in the product UI.
{% endhint %}

### At a glance

| You want to…                               | Start here                | You leave with…                  |
| ------------------------------------------ | ------------------------- | -------------------------------- |
| Run your first week without thrash         | Quickstart                | A repeatable checklist           |
| Understand the credit wallet               | How credits work          | Clear spend before you click     |
| Learn what each screen does                | Workspace tour            | A mental model of the product    |
| Know what you do **not** need to configure | What ARIA handles for you | Confidence that setup is minimal |

### The pipeline

One spine. Every screen follows the same order:

```
Ideas → Validate → Hire → Portfolio → Strategy → Build → MVP
```

<table><thead><tr><th width="87">Stage</th><th width="131">Screen</th><th>Job in one line</th></tr></thead><tbody><tr><td>1</td><td><strong>Ideas</strong></td><td>Discover and score opportunities from real market signals</td></tr><tr><td>2</td><td><strong>Validate</strong></td><td>Pressure-test one idea and get a dossier with a verdict</td></tr><tr><td>3</td><td><strong>Hire</strong></td><td>Generate the MVP build spec for a validated idea</td></tr><tr><td>4</td><td><strong>Portfolio</strong></td><td>See every idea across distribution, waitlist, landing, and MVP</td></tr><tr><td>5</td><td><strong>Strategy</strong></td><td>Turn validation into a channel plan and messaging</td></tr><tr><td>6</td><td><strong>Build</strong></td><td>Ship a waitlist or product landing page to a live URL</td></tr><tr><td>7</td><td><strong>MVP</strong></td><td>Provision and deploy a production-ready app</td></tr></tbody></table>

### Choose your path

**First hour**

* [ ] Read Quickstart
* [ ] Buy credits from the header wallet
* [ ] Run **Generate ideas** on the Ideas board

**First ship**

* [ ] Validate one idea (10 credits)
* [ ] Tap **Hire** to generate the MVP spec (10 credits)
* [ ] Open **Portfolio** and run Strategy, then Build

**First live app**

* [ ] Confirm the MVP spec shows **ready** on the Ideas card
* [ ] Ship a landing page from Build if Portfolio requires it
* [ ] Run **Build MVP** (150 credits) from the MVP screen


---

# 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://docs.ariaagi.com/getting-started/home.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.