Connect Claude or ChatGPT to your business
You can point the AI you already use at your own DISTRYB data and ask it questions in plain English — what's running low, who hasn't paid me, which orders need accepting, what's selling in my state. No dashboard, no exports, no copying figures into a spreadsheet.
This works with Claude Desktop, ChatGPT, Cursor, or anything else that speaks MCP (Model Context Protocol). It is on every plan, and any active team member can set it up.
Setting it up
- Open Developer in the dashboard.
- Create an AI key. You will get a
dk_live_…value — copy it now, because it is not shown again. - Paste the setup snippet into your AI client. For Claude Desktop that is:
npx mcp-remote https://distryb.com/api/mcp/tenant --header "Authorization: Bearer dk_live_…"Other clients take it as a custom connector pointing at https://distryb.com/api/mcp/tenant with the same Authorization: Bearer header.
Then ask it something. It can see inventory, orders, invoices, state registrations and demand.
Looking versus acting
A new key can only look. Tick let it make changes when you create it and it can act as well — accept an order, correct a stock count, propose a payment.
Leave it unticked if you only want answers. You can always make a second key.
A key can never do more than the person who made it
This is the part worth understanding, because it is what makes handing an AI a key reasonable at all.
A key carries that member's current permissions, checked live. So:
- a bartender's key works orders and cannot touch money
- a bookkeeper's key records payments and cannot fulfil
- a key stops working the moment its owner leaves the team, or has a permission taken away
- promote someone and their key gains exactly the reach they do
Nobody can mint themselves extra authority by going through an AI. The same rule applies to PLUG inside the dashboard: it offers each member the tools their role allows, not the full set. If a teammate mentions a tool that has disappeared, that is why — an owner can grant it back under Settings → Team → Roles.
Anything it cannot take back waits for you
Some changes do not just happen. Recording a payment, removing stock, registering a SKU in a new state and cancelling an order all appear under Pending approvals on the Developer page, with the exact change spelled out. Nothing moves until a person clicks Approve.
Accepting an order and correcting a stock count go straight through, because both can simply be done again.
Approving runs the change as you — so you can only wave through something you could have done by hand. Two people clicking Approve at the same moment cannot record the same payment twice.
The payment threshold
If small payments are not worth your time, set a limit on the same page. Payments at or under it get recorded straight away; anything larger still waits.
It starts at $0 — every payment waits — until you deliberately change it, and only someone who can record payments by hand is allowed to set it.
What it is not
It is not the REST API. The Enterprise REST API is a separate thing with its own keys and its own documentation, for building software against DISTRYB. This is for pointing an assistant at your own business.
It is not the public endpoint. https://distryb.com/api/mcp (no /tenant) is the anonymous, public-data server — the licensing directory and the Bottl.Service catalog. It carries no key and sees nothing of yours.
If something is missing
Ask the assistant for its tool list rather than assuming a tool exists — the set you get is the intersection of the key's scope and your current permissions, so it is genuinely different between two people in the same organization. If a tool you expect is absent, check your role first.