Skip to main content
Orbbit Data has its own connector, so you can ask an AI assistant for commodity and branded-food data in plain words. The assistant picks the right tool, 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 MCP: that one lets an assistant read these pages, while this one fetches Orbbit’s data. Connector address: https://data-api.orbbit.co/mcp Your console’s MCP page shows the same address with a copy button.

​
Claude (web, desktop, mobile)

See Use With Claude for step-by-step instructions with a screenshot.

​
Claude Code

Run this, then sign in to Orbbit and click Allow when your browser opens:

​
What the assistant can do

The connector gives the assistant five tools, one per endpoint. Each tool takes the same inputs as its endpoint, and its title is the endpoint’s name in the API Reference. If you connect with an API key, the assistant only sees the tools that key is scoped to. Every tool only reads data. A typical question about prices takes two tools: list_commodities to find the series, then get_commodity_metric_values to get its values. Two things differ from calling the API yourself, to keep answers small enough for the assistant to read:
  • When the assistant doesn’t set limit, list_commodities and search_branded_foods return 10 rows per page.
  • When the assistant doesn’t set start_date, get_commodity_metric_values returns each series’ recent stretch, the same as the API does. See Commodities.
Every tool call goes through the same API as a direct request with your key, so the answer matches what you’d get from the API yourself. Each call to a paid tool is charged like any other. See Pricing & Billing.