How connections work

Through the vendor’s own API

Control Center works through the documented API each vendor publishes, using access you grant in that tool, such as an API key or an app you approve.

Scoped per client

Every integration is enabled per tenant with the exact API operations you allow, and nothing else.

Logged, and approved by a person

Every document, price, workflow and approval is logged with who, when and on what input. A person approves before any client sees anything.

Keys stay in the vault

API keys and passwords live in Control Center’s vault. Your team’s AI never sees them, and nothing is pasted into a chat.

Your AI follows the same rules

Your team reaches the same tools from Claude or ChatGPT through Control Center MCP, with the same roles and client scopes as their login.

Before you connect a tool

• An admin sign-in for the tool.
• A plan that includes API access. A few vendors keep it to certain plans, and each tool’s page says so.
• Permission to create an API key or register an app in the tool.
• Your region or instance address, where the vendor uses one.

Each tool’s page in Every tool lists what that vendor needs on top of this.

Where each vendor’s API docs are

Public docs

Anyone can read the vendor’s API docs.

Docs need a login

You sign in with a customer or partner account to read them.

Partner access

The vendor opens its API through a partner or developer program, so the connection depends on the vendor’s approval.

A tool that isn’t listed

If it has a documented API, Control Center can connect to it. Email us the tool’s name and a link to its API docs.