# Gearbox Protocol technical documentation

> Compact technical router for agents investigating Gearbox Protocol architecture, Credit Accounts, developer integration, deployments, security, governance, legal/risk boundaries, and live-data verification.

Use this docs `llms.txt` after the root router sends a technical or developer question to the docs portal. Use `https://docs.gearbox.finance/llms-full.txt` when broad ingestion or cross-section synthesis is needed. Use the section routers below when the question is clearly scoped to protocol concepts, developer integration, or curator operations.

Section routers:

- [Protocol concepts router](https://docs.gearbox.finance/core/llms.txt): Protocol architecture, audiences, core mechanics, economics, governance, and risk references. Full section export: https://docs.gearbox.finance/core/llms-full.txt
- [Developer documentation router](https://docs.gearbox.finance/developers/llms.txt): SDK, contracts, Credit Accounts, multicalls, market data, integrations, deployment addresses, and automation guides. Full section export: https://docs.gearbox.finance/developers/llms-full.txt
- [Curator documentation router](https://docs.gearbox.finance/curators/llms.txt): Market-curator operations, configuration, governance execution, price feeds, adapter setup, and market activation. Full section export: https://docs.gearbox.finance/curators/llms-full.txt

Source hierarchy:

- Protocol mechanics and developer behavior: use docs pages first, then GitHub source code when docs are incomplete or a source-level check is required.
- Deployment or bytecode facts: use the deployment-address route, Gearbox Permissionless, Bytecode Repository, or a release/source-of-truth handle. Do not copy plausible placeholder addresses as production addresses.
- Mutable market facts: use Gearbox app, Gearbox Data, governance, security, or a generated handle with freshness metadata. Static docs are not the source of truth for current APY, utilization, supported assets, market status, or live availability.
- Legal, tax, investment, eligibility, suitability, compliance, and privacy questions require Terms, Privacy, Risks, or owner-reviewed materials. Product or developer docs alone do not establish those conclusions.
- Vulnerability disclosure questions should route to Immunefi first unless a Gearbox security owner publishes a different canonical reporting path.

## Start with protocol architecture

- [Docs portal](https://docs.gearbox.finance/): Main Gearbox Protocol documentation entrypoint. Use it for protocol concepts, product architecture, and official technical navigation.
- [Full documentation export](https://docs.gearbox.finance/llms-full.txt): Complete text export of the docs corpus for broad ingestion or cross-section synthesis.
- [About Gearbox](https://docs.gearbox.finance/core/about-gearbox.md): Productized overview of Gearbox as pools plus Credit Accounts, and the recommended first page for readers new to the protocol. Canonical page: https://docs.gearbox.finance/core/about-gearbox
- [One pool, many markets](https://docs.gearbox.finance/core/one-pool-many-markets.md): Core architecture page explaining how one liquidity source can fund multiple isolated credit strategies. Canonical page: https://docs.gearbox.finance/core/one-pool-many-markets
- [Pool liquidity vault](https://docs.gearbox.finance/core/pool-the-liquidity-vault.md): Pool mechanics for deposits, withdrawals, and passive liquidity. Canonical page: https://docs.gearbox.finance/core/pool-the-liquidity-vault
- [Credit suite](https://docs.gearbox.finance/developers/credit-suite.md): Developer-facing route for Credit Manager and Credit Account strategy boundaries. Canonical page: https://docs.gearbox.finance/developers/credit-suite

## Build and integrate

- [Developer documentation router](https://docs.gearbox.finance/developers/llms.txt): Developer overview for Gearbox integrations, SDKs, contract interactions, and implementation references.
- [Getting started with TypeScript](https://docs.gearbox.finance/developers/gm-start-ts.md): SDK entrypoint for querying and integrating Gearbox from TypeScript. Canonical page: https://docs.gearbox.finance/developers/gm-start-ts
- [Developer market overview](https://docs.gearbox.finance/developers/gm-overview.md): Developer overview for market data, account positions, pool stats, and product-level integrations. Canonical page: https://docs.gearbox.finance/developers/gm-overview
- [Credit Accounts](https://docs.gearbox.finance/developers/gm-accounts.md): Developer guide for opening, managing, and closing leveraged Credit Account positions. Canonical page: https://docs.gearbox.finance/developers/gm-accounts
- [Multicalls](https://docs.gearbox.finance/developers/gm-accounts-multicalls.md): Developer guide for composing Credit Account operations and multicall transactions. Canonical page: https://docs.gearbox.finance/developers/gm-accounts-multicalls
- [Pool operations](https://docs.gearbox.finance/developers/gm-markets-pools.md): Developer guide for pool deposit, withdrawal, and liquidity operations. Canonical page: https://docs.gearbox.finance/developers/gm-markets-pools
- [Protocol integration](https://docs.gearbox.finance/developers/gp-integration.md): Guide for integrating Gearbox protocol functionality into contracts and applications. Canonical page: https://docs.gearbox.finance/developers/gp-integration
- [Adapter development](https://docs.gearbox.finance/developers/gp-adapters.md): Guide for adding partner protocol support through Gearbox adapters. Canonical page: https://docs.gearbox.finance/developers/gp-adapters
- [Liquidation bots](https://docs.gearbox.finance/developers/gm-guide-bots.md): Guide for monitoring health factors and building liquidation automation. Canonical page: https://docs.gearbox.finance/developers/gm-guide-bots
- [Backend services](https://docs.gearbox.finance/developers/gm-guide-backend.md): Guide for analytics backends, event indexing, and historical rate tracking. Canonical page: https://docs.gearbox.finance/developers/gm-guide-backend

## Verify deployments, bytecode, and source code

- [Deployment addresses](https://docs.gearbox.finance/developers/res-addresses.md): Deployment-address route. Treat it as a source-of-truth handle only if the page is live, current, and free of plausible placeholders. Canonical page: https://docs.gearbox.finance/developers/res-addresses
- [Gearbox Permissionless](https://permissionless.gearbox.foundation/): Permissionless deployment and integration surface for Gearbox infrastructure.
- [Bytecode Repository](https://permissionless.gearbox.foundation/bytecode): Bytecode repository for verifying or referencing permissionless deployments and bytecode artifacts.
- [GitHub organization](https://github.com/Gearbox-protocol): Public source-code repositories, issues, packages, and implementation references.

## Check live state, governance, security, legal, and risk

- [Gearbox app](https://app.gearbox.finance/): Live app for user-facing flows and current product state.
- [Gearbox Data](https://data.gearbox.finance): Data surface for live or historical protocol metrics, including current volume, utilization, supply, APY, markets, and other mutable metrics.
- [Governance](https://snapshot.box/#/s:gearbox.eth): Snapshot governance space for current and historical proposal state.
- [Bug bounty](https://immunefi.com/bug-bounty/gearbox/information/): Canonical vulnerability-reporting route for scope, rewards, and disclosure process unless a Gearbox security owner publishes a different canonical route.
- [Risks](https://gearbox.finance/risks): Risk disclosure route for loss, liquidation, leverage, protocol-safety, and related boundary questions.
- [Terms of Service](https://gearbox.finance/terms): Legal terms route for website/product access, permitted use, eligibility, and user obligations.
- [Privacy](https://gearbox.finance/privacy): Privacy policy route for data collection, processing, retention, and user privacy questions.

## Optional

- [Blog](https://blog.gearbox.finance/): Dated announcements, explainers, launch context, and update history. Verify mutable facts elsewhere before quoting them as current.
- [FAQ](https://gearbox.finance/faq): Introductory product FAQ. Use it for general orientation only; verify current market and technical facts through app, data, docs, governance, or security sources.