> For the complete documentation index, see [llms.txt](https://docs.build.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.build.fun/create-an-agent/stocks-example.md).

# Example (Stocks)

{% hint style="info" %}

#### **Full video walkthrough guide coming soon**

{% endhint %}

#### **Stocks Monitoring & Auto-Trading**

* **Goal**: Track stock tickers or crypto prices in real time, execute trades under certain conditions.
* **Key Functions**:
  * `get_token_info` to retrieve live market data.
  * `execute_trade` (custom) that interacts with a brokerage or on-chain DEX.
  * `search_twitter` for sentiment analysis or relevant news.
* **Workflow**: The agent monitors $APPL or $ETH, compares the data with your custom rules (e.g., “buy if price dips 5%”), and automatically trades. Perfect for users who want an always-on “mini hedge fund” that capitalizes on market movements day or night.


---

# 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.build.fun/create-an-agent/stocks-example.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.