> For the complete documentation index, see [llms.txt](https://devs-aco.gitbook.io/devs-aco-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://devs-aco.gitbook.io/devs-aco-docs/information/how-we-operate.md).

# How We Operate

What happens from signup to checkout.

### The process

1. Read these docs, then open a ticket in #open-a-ticket.
2. Set up your Amazon account using the **Amazon Requirements** and **Amazon 2FA Setup** guides.
3. Submit your profile through the encrypted form.
4. We load your profile and run it on upcoming drops.
5. When we check out for you, we message you with what was ordered and what you owe.
6. Pay your PAS and you stay in the rotation for the next drop.

### No guarantees

Drops are competitive. We run every profile the same way, but we can't promise a checkout on any specific drop. If nothing checks out, you owe nothing.

### Built for resellers

We mainly run NeeDohs, plus Pokémon and other hype items when they drop. We aim for the max profitable quantity on each drop, not one or two for personal use. There are no custom item lists or custom quantities per person.

### Payment

PayPal Friends & Family only. See **Paying PAS**, **PAS Cost**, and the **Terms of Service**.


---

# 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://devs-aco.gitbook.io/devs-aco-docs/information/how-we-operate.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.
