> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trycherry.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Cherry keeps your books. The API and MCP server let your systems read them — and write to them.

Cherry is your AI accountant. It categorizes transactions, keeps a double-entry ledger, watches your obligations, and produces your financial statements.

The public API and MCP server expose those books to your own software and agents:

* **REST API** at `https://api.trycherry.ai/v1` — read transactions, the chart of accounts, journal entries, trial balance, and financial statements; push bank accounts and transactions without connecting Plaid.
* **MCP server** at `https://api.trycherry.ai/mcp` — the same capabilities as tools for Claude, ChatGPT, or any MCP-capable agent.

Both use the same API keys, scoped to one business.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Create a key and make your first request in two minutes.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    How keys, scopes, and tenancy work.
  </Card>

  <Card title="Push your own transactions" icon="building-columns" href="/guides/manual-banks">
    Create bank accounts and push transactions without Plaid.
  </Card>

  <Card title="Connect an agent over MCP" icon="plug" href="/guides/mcp">
    Point any MCP client at your books.
  </Card>
</CardGroup>

## What happens to data you push

Transactions you push enter the same pipeline as bank-connected ones: Cherry categorizes them against your chart of accounts, books journal entries, and folds them into your statements. You don't post to the ledger directly — Cherry does the accounting.