> ## Documentation Index
> Fetch the complete documentation index at: https://readme.amana-dev.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Platform Overview

> Map your brokerage or trading application to the capabilities and responsibilities of your partnership.

Start with the product you want to offer your clients, then confirm the Amana capabilities required to support it.

## Integration Areas

| Area | What to plan |
| - | - |
| Client onboarding | Identity verification, eligibility, and the agreed account-provisioning workflow. |
| Trading accounts | Account access, balances, and the information displayed to clients. |
| Market data | Instrument discovery, pricing, and historical data requirements. |
| Trading | Order entry, order status, positions, and client-facing risk information. |
| Funding and transactions | Supported payment flows, transaction history, and exception handling. |

Confirm the availability and scope of each area with Amana before including it in your product. An area listed here is not a promise that every related workflow or endpoint is available to every partner.

## Define the Partner Scope

Agree the markets, instruments, client journeys, and environments your integration will support. Confirm the account model and the relationship between your application users and their trading accounts.

## Agree Responsibilities

Document the responsibilities for onboarding, regulatory obligations, client disclosures, payments, client support, and incident response. API access alone does not establish commercial terms or permission to operate a brokerage.

Continue with [partner onboarding](/get-started/onboarding) and [integration architecture](/integration-guides/architecture).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.