> For the complete documentation index, see [llms.txt](https://crypto.phbot.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crypto.phbot.org/exchanges/introduction.md).

# Introduction

## Supported Exchanges

More exchanges may be added in the future depending on demand.

* Binance.com / Binance.us
* Coinbase
* Gemini
* Alpaca (stocks/crypto)
* Kraken

## Date / Time

**Your computer timezone and time must be correct otherwise you will have issues authenticating.**

## Configuration

All settings are stored inside the `phBot.ini` file where the executable lives. You only need one exchange for phBot to function. Binance currently has the lowest fees and is available almost everywhere. Coinbase Pro has much higher fees until you start doing lots of volume.

The `db3` files are where order and fill information is stored (per exchange). They can be deleted if needed only when `Switched` is disabled and you are not taking profit as crypto. See [Switched](broken://pages/KMDIF79Sv455qrqEuoDX) for more info.

## API Key Creation

First you will need to create an API key so that the bot is able to make trades. *Do not ever* share the API keys you create with someone else.


---

# 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://crypto.phbot.org/exchanges/introduction.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.