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

# Altimate AI

> Connect Altimate AI to Paradime so every production Catalog refresh sends your dbt™ manifest, catalog, and semantic manifest to your Altimate AI instance.

[Altimate AI](https://www.altimate.ai/) is a data engineering platform with AI tools for dbt™ projects. Connecting Altimate AI to Paradime keeps your Altimate AI instance up to date with your dbt™ project: Paradime sends your dbt™ artifacts to Altimate AI after every production Catalog refresh, with no command to add.

![Paradime and Altimate AI logos side by side, with the caption Send dbt artifacts to Altimate AI automatically](https://mintcdn.com/paradime-docs/xT8TN4y9Md_1nyum/images/paradime-altimate-ai-integration.jpg?fit=max\&auto=format\&n=xT8TN4y9Md_1nyum\&q=85\&s=efd22a5e5ff38add4b8a15a9b4ede9c0)

## What you can do

* Keep Altimate AI in sync with your production dbt™ project, without a separate upload job.
* Send `manifest.json`, `catalog.json`, and, when your project has one, `semantic_manifest.json` from each production Catalog refresh.
* Connect once per workspace from **Settings** > **Integrations**, with a credential check before the connection is saved.

## Prerequisites

> [!NOTE]
>
> Before you connect, make sure you have:
>
> * An Altimate AI instance, and its instance name (also called the tenant name).
> * A **dbt Core** integration in Altimate AI, and its integration ID.
> * An Altimate AI API token that can upload to that integration.
> * The Admin role in Paradime, to connect the integration.

## Step 1: Get your Altimate AI details

In your Altimate AI instance, find these values:

1. **Instance name**: the name of your Altimate AI instance (tenant).
2. **dbt Core integration ID**: the ID of the dbt Core integration that receives your artifacts. Create one in Altimate AI if you don't have one yet.
3. **API token**: an API token for your instance. Store it securely. Paradime keeps it in a secret store and never shows it again.

## Step 2: Connect Altimate AI in Paradime

1. In Paradime, go to **Settings** > **Integrations** (see [connecting integrations](https://docs.paradime.io/integrations/connecting-integrations.md)).
2. In the **Data Catalog** section, find **Altimate AI** and click **Connect**.
3. Fill in the fields:

| Field | Required | Description |
| - | - | - |
| **Instance name** | ✅ | Your Altimate AI instance (tenant) name. |
| **dbt Core integration ID** | ✅ | The ID of your Altimate AI dbt Core integration. |
| **API Token** | ✅ | Your Altimate AI API token. |
| **Environment name (optional)** | Optional | The Altimate AI environment the artifacts belong to. Defaults to `PROD`. |
| **Backend URL (optional)** | Optional | The Altimate AI API URL. Defaults to `https://api.myaltimate.com`. It must be a public `https://` URL. |

4. Click **Test connection**. Paradime checks the credentials with Altimate AI and saves them only if the check passes. When it passes, the form shows "Paradime can now send dbt artifacts to Altimate AI." Click **Close**.

If the check fails, the form shows the error from Altimate AI, or "We couldn't connect to Altimate AI. Check your credentials and try again." Fix the values and click **Try again**.

## When Paradime sends artifacts

Paradime sends artifacts at the end of every **production** Catalog refresh in the workspace, scheduled or on demand. It uses the Altimate DataPilot CLI (`datapilot dbt onboard`) and sends:

* `manifest.json`
* `catalog.json`
* `semantic_manifest.json`, when your project produces one

It doesn't send `run_results.json` or `sources.json`. Development catalog refreshes in the Code IDE don't send anything.

To control when the push runs, schedule the [Paradime Catalog Refresh](https://docs.paradime.io/products/bolt/creating-schedules/command-settings/paradime-refresh-catalog.md) command in Bolt.

> [!NOTE]
>
> A push that fails never fails the Catalog refresh or the Bolt run. Paradime writes the error to `altimate_push_error.json` in the run's artifacts instead.

## Troubleshooting

### The refresh succeeds but nothing appears in Altimate AI

A green run doesn't mean the push succeeded, because a failed push doesn't fail the run.

> [!TIP]
>
> 1. Check that Altimate AI is connected in the workspace you refresh. Each workspace has its own connection.
> 2. Look for `altimate_push_error.json` in the artifacts of the production Catalog refresh. It holds the error from Altimate AI.
> 3. Check that the API token still works and can upload to the dbt Core integration ID you entered. If not, disconnect and connect again with a new token.

## Disconnecting

Go to **Settings** > **Integrations**, find **Altimate AI**, and click **Disconnect**. Paradime deletes the stored token, and the next production Catalog refresh sends nothing.


## Related topics

- [Push dbt™ artifacts to Altimate AI on Catalog refresh](https://docs.paradime.io/changelog/2026-10-29/altimate.md)
- [Integrations](https://docs.paradime.io/integrations/index.md)
- [Changelog](https://docs.paradime.io/changelog/overview.md)
- [Automate with AI agents](https://docs.paradime.io/guides/programmable-agents/index.md)
- [Claude Desktop & claude.ai](https://docs.paradime.io/products/dino-ai/mcp-server/claude-desktop.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.