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

# Why Amoeba Farm

Amoeba Farm exists because some of the most important input markets are hard to see and harder to trade.

Memory, storage, and other hardware inputs sit under AI infrastructure, consumer devices, servers, cloud buildouts, and supply-chain planning. Their price signals matter, but the data is scattered and inconsistent.

## The Problem

A single hardware market can be described by:

* public retailer pages;
* distributor catalogs;
* manufacturer stores;
* benchmark assessments;
* public API series;
* procurement quotes;
* broker channels;
* stale listings.

Those sources do not all mean the same thing. Some are public and repeatable. Some are private. Some are stale. Some describe the wrong product. Some are useful only when compared against themselves over time.

## The Amoeba Farm Approach

Amoeba Farm does not claim there is one perfect live spot price for every hardware input.

Instead, it asks a more practical question:

```
Can a defined market publish a repeatable monthly recipe,
measure accepted sources against their own opening values,
and settle fixed-risk contracts from the result?
```

That is the core of Amoeba Farm.

## Why This Helps

For traders, it creates direct exposure to a hardware cycle that is usually expressed through noisy proxies.

For contributors, it creates paid work around source discovery, evidence, updates, and challenges.

For builders, it creates a public data and settlement layer that can later support deeper hardware-market products.

## The First Promise

Trade monthly hardware benchmark moves with fixed maximum loss and transparent oracle settlement.


---

# 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.amoeba.farm/overview/01-why-amoeba-farm.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.