Kilevel
Dashboard

Language / Sprache

KILEVEL © 2026

Integrations

Kilevel and Ki in your AI assistant

Two separate connections for ChatGPT, Claude, Gemini, Grok and other MCP clients. Kilevel brings in your business workspace, Ki brings in your personal assistant. Connect one or both: each has its own address, its own sign-in and its own permissions.

Kilevel

Your workspace

For businesses & enterprises

ForKitalkKios

Build and run your AI agents from the chat

Describe the agent you need, try it and put it live without leaving the assistant. Your agents, phone numbers and usage stay in your Kilevel account, so you can start in one assistant and go on in another, or in the app.

What the assistant can do

  • Draft an agent: from a description, for voice or chat. Kilevel writes its instructions, and it stays a draft until you connect it.

  • Try it: in text, with the assistant playing a contact. To talk to it, a link opens the agent in Kilevel.

  • Put it live: on a phone number or your website, once you have seen what will change and agreed. In Claude, you connect numbers in the app, and Claude gives you the link.

  • See how it went: outcomes, summaries and performance of calls and chats. Full conversations only if you turn them on.

Outbound calls and campaigns stay in the app and the API, where you set them up with your own consent records.

Where each assistant stands

Server address

https://api.kilevel.com/api/mcp/workspace

By address means it is not in the assistant’s directory yet: you add the server address yourself, which takes a minute, and the guide shows the steps. The assistant’s own plan has to allow custom connectors, and Google offers Gemini’s in the US for now. In Grok Business and Enterprise, a team admin adds the connector first.

  • Your account: Sign in with your Kilevel account. Usage and billing stay with Kilevel, and assistants cannot buy anything.

  • Your control: Under API › AI assistants, the account owner sees each connected assistant and what it did, and can cut one off at once.

  • Your data: An assistant reads what you allow, when you ask it something. Kilevel does not see your conversation with the assistant.

Ki

Your personal assistant

For personal use, professionals & teams

Bring what Ki knows about you into every chat

The AI chat you use every day can ask Ki what it knows about you, and hand Ki what is worth keeping. You decide what it gets to see.

What the assistant can do with Ki

  • Ask for context: who you are, your open tracks, the next seven days, what you decided and your world, only as far as the question needs.

  • Hand Ki a note to remember: it waits for review before Ki takes it in. Passwords, codes and card numbers are refused.

  • Suggest a commitment: it arrives as a suggested track that you accept first.

  • Ask where things stand: on the tracks Ki keeps for you.

  • Work with your team: read the boards of the teams you are in, and have Ki change a track or comment on it for you, as far as your role and the team allow.

  • Delegate: it becomes an approval in Ki. Nothing happens until you say yes.

Never, whatever your switches: other people’s numbers and addresses, your contact book, bank and tax numbers, codes, PINs and passwords, and the transcripts of your calls.

Where each assistant stands

Server address

https://api.kilevel.com/api/mcp/ki

By address means it is not in the assistant’s directory yet: you add the server address yourself, which takes a minute, and the guide shows the steps. The assistant’s own plan has to allow custom connectors, and Google offers Gemini’s in the US for now. In Grok Business and Enterprise, a team admin adds the connector first.

  • Your Power: Connecting needs a Power of Ki that includes AI apps.

  • Your switches: Under Connections › AI apps, each kind of information has its own switch. Your health and your finances stay off until you turn them on.

  • Your yes: What an app hands over waits for review, and a request to act waits for your approval. Revoke ends an app’s access at once.

How connecting works

  1. Add it to the assistant

    From the assistant’s directory where it is listed, or with the server address.

  2. Sign in

    A Kilevel page opens. Sign in, or create an account if you do not have one yet.

  3. Choose what it may do

    You see each permission the assistant asks for, and you decide.

  4. Disconnect whenever you like

    Access ends as soon as you remove it.

For developers and IT

  • Authentication: OAuth 2.1 with PKCE. There is no API key to paste, and passwords stay with Kilevel.

  • Two separate servers: Kilevel and Ki each have their own address, and a sign-in for one gives nothing on the other.

  • Control: Account owners decide which assistants may connect to the workspace. With Ki, each person decides for themselves.

Building on Kilevel?

For every tool, outbound calls included, use an API key with the Kilevel MCP server.

The Kilevel MCP server

See it on your own calls

Start with a test number and a small set of real questions. Nothing has to change on your main line until you decide it should.