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

# Introduction

> AI-native error monitoring with built-in triage, flexible ingestion, and fix workflows.

Squasher helps you capture errors, route logs, and investigate incidents from one place.

## What Squasher gives you

* AI triage on every new error group so you get a summary, severity, and fix direction faster.
* SDK-based error capture for application-level context.
* Log drains for infrastructure and platform errors when you do not want to install an SDK.
* Alerting, status monitoring, and hosted fix workflows in the same product.

## Start with the right path

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Set up Squasher in a Next.js app, Node.js service, or provider log drain.
  </Card>

  <Card title="Agent DX" icon="sparkles" href="/agents">
    Give coding agents the docs, API, CLI, and MCP entry points they should use.
  </Card>

  <Card title="Next.js SDK" icon="react" href="/sdks/nextjs">
    Capture route, server, and client errors with framework-aware helpers.
  </Card>

  <Card title="Node.js SDK" icon="node-js" href="/sdks/node">
    Instrument Express, Fastify, Hono, Bun, or plain Node.js services.
  </Card>

  <Card title="Vercel log drain" icon="cloud" href="/integrations/vercel">
    Start with zero-code capture for deployment and runtime logs.
  </Card>
</CardGroup>

## Supported paths

| Use case                       | Recommended guide                                                                                                   |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------- |
| Next.js application monitoring | [Next.js SDK](/sdks/nextjs)                                                                                         |
| Node.js service monitoring     | [Node.js SDK](/sdks/node)                                                                                           |
| Browser-only monitoring        | [Browser SDK](/sdks/browser)                                                                                        |
| AI runtime telemetry           | [Agent telemetry SDK](/sdks/agent)                                                                                  |
| Structured application logs    | [Pino transport](/sdks/pino) or [Winston transport](/sdks/winston)                                                  |
| Provider log forwarding        | [Vercel](/integrations/vercel), [Railway](/integrations/railway), or [cloud log drains](/log-drains/aws-cloudwatch) |

## For agents

Start with [Agent DX](/agents) or `https://docs.squasher.ai/llms.txt`.

Use this routing:

* **Need to change app code**: pick the SDK guide for the runtime, initialize early, and send one verification event.
* **Need live Squasher data**: connect the [MCP server](/integrations/mcp), call `search`, then call `execute` for the exact operation.
* **Need repeatable terminal commands**: use the [CLI setup guide](/integrations/cli-oauth) and include `--project <project_id>`.
* **Need custom integration code**: use the [API reference](/api-reference/introduction) and OpenAPI contract.

## Next steps

1. Follow the [quickstart](/quickstart).
2. Configure the SDK or integration that matches your runtime.
3. Review [troubleshooting](/troubleshooting) if your first events do not appear.