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

# Accounts and portfolio management

In the Architect PMS, portfolios are represented as accounts, which contain balances and positions. Accounts are mapped one-to-one with their correspondent on each venue, exchange, or clearing entity. All Architect-managed accounts are uniquely identified by UUID. The following are some examples of different kinds of accounts:

| Account                                 | Example accout name                           | Description                                                               |
| --------------------------------------- | --------------------------------------------- | ------------------------------------------------------------------------- |
| US futures and options clearing account | STONEX:ABC123/JohnDoe                         |                                                                           |
| US equities clearing account            | DORMAN:44444R/BLast                           |                                                                           |
| Coinbase portfolio                      | COINBASE:a2868946-2b80-4b9e-a672-cdda4bb200dc | For prop trading, the portfolio ID of a connected Coinbase crypto account |

### Balances and positions

Account balances describe the amount of cash or assets held; for example, an account may hold 5 BTC or 20 shares of AAPL, and have a margin balance of 1000 USD. 

Positions represent ownership or exposure to financial instruments in an account; for example, an account may be net short 10 shares of TSLA or net long 3 CME GC contracts. By default, positions are unaggregated and separate orders in the same instrument will result in distinct positions.


---

# 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://docs.architect.co/concepts/portfolio-management.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.