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

# Connect Orbbit Data to Your AI Assistant

> Add Orbbit's data connector to Claude or Claude Code so your assistant can look up and call Orbbit endpoints for you.

Orbbit Data has its own connector, so you can ask an AI assistant for commodity, branded-food, and store data in plain words. The assistant finds the right endpoint, calls it with your account, and answers from the result.

It uses MCP (Model Context Protocol), the standard way AI tools plug into outside sources. This is a different connector from the [docs connector](/ai-agents): that one lets an assistant read these pages, while this one fetches Orbbit's data.

Connector address: `https://api.orbbit.co/mcp`

Your console's **MCP** page shows the same address with a copy button.

## Claude (web, desktop, mobile)

1. In Claude, open **Customize** → **Connectors** → **Add** → **Add custom connector**.
2. Name it `Orbbit Data`, paste the connector address, click **Add**, then **Connect**.
3. Sign in to Orbbit and click **Allow**.

The assistant can now call every endpoint your account can.

## Claude Code

<Tabs>
  <Tab title="Sign in">
    Run this, then sign in to Orbbit and click **Allow** when your browser opens:

    ```bash theme={null}
    claude mcp add --transport http orbbit-data https://api.orbbit.co/mcp
    ```
  </Tab>

  <Tab title="API key">
    Connect with one of your [API keys](/authentication) instead of signing in:

    ```bash theme={null}
    claude mcp add --transport http orbbit-data https://api.orbbit.co/mcp \
      --header "Authorization: Bearer orbbit_data_YOUR_KEY"
    ```

    The assistant can only call the endpoints that key is scoped to. Revoking the key cuts the connection off.
  </Tab>
</Tabs>

## What the assistant can do

The connector gives the assistant three tools, which it uses in this order:

| Tool                | What it does                                                          |
| ------------------- | --------------------------------------------------------------------- |
| `list-endpoints`    | Lists the endpoints this connection is allowed to call.               |
| `describe-endpoint` | Shows one endpoint's parameters, so the assistant knows what to send. |
| `call-endpoint`     | Calls the endpoint and returns exactly what the API would return.     |

Every call goes through the same API as a direct request with your key, so the answer matches what you'd get from the [API Reference](/api-reference/introduction).