FOR DEVELOPERS

Your software can ask too.

Official libraries for Python and Node, and a drop-in chat for your own web app. Ask questions, manage conversations, projects, files and scheduled jobs, and put the chat in front of your users — with keys your admin hands out and can take back, and the same permissions your people already have.

Your API key stays on your server. Browsers get a one-time sign-in code, every call runs with a real person's permissions, and anything held for approval still waits for a human click inside InsideAI.

THE LIBRARIES

Three ways in, two packages.

Python for your back office, Node for your servers, and a drop-in chat for the pages your users already use. The two server clients do the same things with the same names, so pick whichever language your team writes.

Python 3

Python

insideai

For scripts, back-office jobs and Django, Flask or FastAPI apps. Everything on this page, from asking a question to managing scheduled jobs.

pip install insideai
View on PyPI
Node 18+

Node server

@cpcyber/insideai/server

The same capabilities as the Python client, for Express, Next.js route handlers and anything else that runs on your own servers.

npm install @cpcyber/insideai
View on npm
Browser · React

Embedded chat

@cpcyber/insideai · @cpcyber/insideai/react

Put the full chat, or a launcher that pops it open, inside your own web app. It knows which page the user is on and takes your colours through CSS variables.

npm install @cpcyber/insideai
View on npm
WHAT YOU CAN BUILD

Most of what your people do in the portal, from code.

Every call runs as a real member of your organization, so it can only reach what that person could reach by signing in.

Ask and get answers

Ask a question and wait for the answer. Choose the model, point it at one knowledge-base folder, attach images, continue a conversation or run it inside a project.

Take the answer with you

Export an answer as a Word document, or any one of its tables as CSV or Excel. You can also read the steps that went into an answer.

Manage conversations

List and search conversations, then rename, archive, favorite or summarize them, or stop one that is still answering.

Projects

List, create and update projects, including the custom instructions the AI follows inside each one.

Knowledge base

Browse folders, upload files and wait until they have been analyzed, so your next question can use them.

Scheduled jobs

List, create, update, delete and run on demand the prompts a member has scheduled to run on their own.

Prompt library

Run a saved prompt by its stable name, so the wording can change inside InsideAI without a code change on your side.

See what is waiting for approval

Read actions that are being held for approval. Your code can only look: approving one still takes a person clicking inside InsideAI.

Embed the chat

Mint a sign-in session on your server and show the chat in your app, either full-page or as a launcher, with page context and your own theme.

QUICKSTART

A first answer in a few lines.

Each one assumes an admin has already given you a key (below). Put it in your server's environment as INSIDEAI_API_KEY.

1. Install

pip install insideai

2. Ask, wait, print

import os
from insideai import InsideAI, create_chat, wait_for_chat

iai = InsideAI(api_key=os.environ["INSIDEAI_API_KEY"])

chat = create_chat(iai, "Summarize this week's open tickets.")
print(wait_for_chat(iai, chat["id"])["answer_text"])
KEYS & SECURITY

Keys your admin hands out, and can take back.

A client admin makes each key, decides who it may act as, and can revoke it the moment it should stop working.

01

An admin creates a key

In the portal, under Tools → API Keys. Give each integration its own key so you can see when each was used and switch one off without touching the rest.

02

Pick what it acts as

A user-specific key always acts as one person. A client-wide key acts as your organization's service account, and may act as any active member by naming them in the act-as header.

03

Keep it on your server

Store it like any other secret. Anything a call creates shows up in the acting person's own history, with their permissions — never more.

Calling the HTTP API directly? Name the member in

X-InsideAI-Act-As

What stays true

The key never reaches a browser. Embedded chat gets a single-use sign-in code that expires within a minute.

Revocable at any time from the portal.

Scoped to your organization: a key can only act as active members of the organization that issued it.

Acting as someone means their permissions exactly, so a key cannot see more than that person could.

Approvals stay human. Your code can see what is held, but only a person inside InsideAI can approve it.

KEEP EXPLORING

Every part of the story is one click away.

EARLY ACCESS

See it on your own systems.

Straight answer on where we are: InsideAI is early. It is deployed and doing real work inside real businesses, and we are taking on a few at a time on purpose — every deployment gets a person on it, not a ticket queue.

Tell us what your team runs on and what you would want it to answer. We will be straight with you about what fits today and what is still ahead, and coming in now means real say in what gets built next.

Talk to us

Reach a person

Already set up with InsideAI?

Sign in to pick up right where your team left off.

Sign In