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

# Developer integrations

> Where things stand for SDKs, n8n, and LangChain, and how to send activity into Velatir today.

## Current status

The earlier generation of Velatir client libraries — PyPI `velatir`, npm `@velatir/sdk`, PyPI `langchain-velatir`, and the n8n community node `n8n-nodes-velatir` — call an API that **no longer exists** on the current platform. They cannot create traces, pause workflows, or wait for an approval. Do not install them against a live organisation.

Replacement clients are in progress and are **not published** yet. There is no package to `pip install` or `npm install` for the current API.

If you are blocked on a programmatic integration, contact [hello@velatir.com](mailto:hello@velatir.com) rather than pinning an older release — no version of those v1 packages still functions.

## How activity reaches Velatir today

<CardGroup cols={2}>
  <Card title="Velatir for Desktop" icon="monitor" href="/desktop-app/overview">
    The supported way to monitor AI use in the browser and on the device, including optional Claude Code and Codex ingest.
  </Card>

  <Card title="Browser extension" icon="globe" href="/setup/browser-extension">
    Browser-only coverage when you do not roll out the desktop client.
  </Card>

  <Card title="Claude Cowork" icon="bot" href="/connectors/claude-cowork">
    Point Cowork's OpenTelemetry export at Velatir. Nothing to install on the device.
  </Card>

  <Card title="AI data specification" icon="file-json" href="/providers/ai-data-specification">
    For software providers: the data model Velatir consumes when connecting to your product.
  </Card>
</CardGroup>

Ingest keys used by Desktop, the extension, and Cowork are created under **Settings → API keys**. See the [quickstart](/quickstart).