OpenAI, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your OpenAI account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Artificial Intelligence
- Connects with a key
- 14 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What OpenAI is
Toolkit for OpenAI APIs: manage Assistants, Threads/Messages; upload/list/delete Files; list/retrieve Models (including vision/multimodal); and view fine-tune listings and events.
You paste in a key from your own OpenAI account. It is kept encrypted, and you can withdraw it from inside OpenAI whenever you like.
One message in, the work done in OpenAI.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in OpenAI. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own OpenAI account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in OpenAI
These are the ready-made tools your AI employee already has in OpenAI. It is not limited to them, but it never has to be taught these.
- Create AssistantTool to create a new assistant with specified parameters. use after finalizing model, tools, and instructions.
- Create MessageTool to create a new message in a specific thread. use when adding messages to an existing conversation after confirming the thread id.
- Create ThreadTool to create a new thread. use when initializing a conversation with optional starter messages.
- Delete assistantTool to delete a specific assistant by its id. use when you need to remove an assistant after confirming its id.
- Delete fileTool to delete a file. use when you need to remove an uploaded file by its id after confirming the target.
- List filesTool to retrieve a list of files. use when you need to view all files uploaded to your organization.
- List fine-tunesTool to list your organization's fine-tuning jobs. use when you need to review all fine-tune runs.
- List modelsTool to list available models. use when you need to discover which models you can call. use after confirming your api key is valid.
- List run stepsTool to retrieve all steps of a specific run. use when you need to inspect each step's details after initiating a run.
- Modify threadTool to modify an existing thread's metadata. use after obtaining the thread id when you need to update metadata.
- Retrieve assistantTool to retrieve details of a specific assistant. use when you need to confirm assistant metadata before performing further operations.
- Retrieve modelTool to retrieve details of a specific model. use when you have a model id and need to confirm its metadata before using it.
- Retrieve threadTool to retrieve details of a specific thread by its id. use when you need to fetch thread metadata before listing messages.
- Upload fileTool to upload a file for use across openai endpoints. use before referencing the file in tasks like fine-tuning.
You stay the boss of your OpenAI account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own OpenAI account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in OpenAI is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in OpenAI and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about OpenAI
- Can an AI employee really work inside OpenAI?
- Yes. It signs in to your own OpenAI account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of OpenAI?
- No. Nothing moves and nothing is replaced. Your records stay in OpenAI, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my OpenAI account?
- You paste in a key from your own OpenAI account. It is kept encrypted, and you can withdraw it from inside OpenAI whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in OpenAI?
- It has 14 ready-made tools in OpenAI today, among them Create Assistant, Create Message and Create Thread. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use OpenAI and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in OpenAI and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in OpenAI?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in OpenAI is written down with what it did and when.