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

# Developer Documentation

The PizzaStack API is TomatoPy's core product. It lets you virtually acquire, prepare, cook, and assemble pizzas programmatically.

## Base URL

```
https://api.tomatopy.pizza/v1
```

## Pipeline

Making a pizza with the PizzaStack API follows a specific pipeline. Each step produces an object whose ID is used in the next step:

1. **Acquire** a tomato → returns a raw tomato object
2. **Slice** the tomato → returns a sliced object (required before cooking)
3. **Simmer** the sliced tomato into a sauce → returns a sauce object
4. **Create a base** → returns a pizza base object
5. **Assemble** the pizza from base + sauce + toppings → returns an assembled pizza object
6. **Bake** the assembled pizza → returns a baked pizza with quality metrics

Each step depends on the previous one. Skipping or misordering steps will not always return an error — instead, quality degrades silently. See [Quality Scoring](https://tomatopy.pizza/docs/developer-documentation/quality-scoring.md) for details.

## Sections

* [Authentication](https://tomatopy.pizza/docs/developer-documentation/authentication.md) — API key and session ID setup
* [Pipeline Overview](https://tomatopy.pizza/docs/developer-documentation/pipeline-overview.md) — End-to-end flow with dependency diagram
* [Quality Scoring](https://tomatopy.pizza/docs/developer-documentation/quality-scoring.md) — How the quality score is computed


---

# 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://tomatopy.pizza/docs/developer-documentation.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.
