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

# Choose an Integration

> Choose between the Planck AI Gateway, automatic logging, manual logging, and custom traces

Choose the integration that matches where your model calls run and whether you want Planck to route them.

| Integration       | Best for                                         | Routes model calls | Sends observability data |
| ----------------- | ------------------------------------------------ | ------------------ | ------------------------ |
| AI Gateway        | New applications and provider switching          | Yes                | Automatically            |
| Automatic Logging | Existing supported provider SDKs                 | No                 | Automatically            |
| Manual Logger     | Existing applications that need explicit control | No                 | From your code           |
| Custom Traces     | Non-LLM steps, tools, and vector databases       | No                 | From your code           |

<CardGroup cols={2}>
  <Card title="AI Gateway" icon="route" href="/getting-started/integration-method/gateway">
    Call supported models through OpenAI-compatible or Anthropic-compatible
    APIs.
  </Card>

  <Card title="Automatic Logging" icon="wave-pulse" href="/getting-started/integration-method/automatic-logging">
    Use the Planck Async Logger while requests continue going directly to your provider.
  </Card>

  <Card title="Manual Logger" icon="code" href="/getting-started/integration-method/manual-logging">
    Send request and response records to Planck explicitly.
  </Card>

  <Card title="Custom Traces" icon="diagram-project" href="/integrations/custom-tracing">
    Add tool calls, retrieval, and application-specific steps to a trace.
  </Card>
</CardGroup>

## Recommended path

Start with the [AI Gateway](/getting-started/integration-method/gateway) when Planck should handle model routing, credentials, and normalized responses. Use automatic or manual logging when provider traffic must remain on its existing path.

You can combine gateway requests with custom traces to capture the rest of an agent workflow.