Sanaf AI
Start free
Artificial Intelligence

Honeyhive, 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 Honeyhive 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
  • 24 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Honeyhive is

HoneyHive is a modern AI observability and evaluation platform that enables developers and domain experts to collaboratively build reliable AI applications faster.

You paste in a key from your own Honeyhive account. It is kept encrypted, and you can withdraw it from inside Honeyhive whenever you like.

How a run works

One message in, the work done in Honeyhive.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Honeyhive. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Honeyhive account, inside the access you granted it, doing the thing you asked for.

  4. 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.

24 tools it already has

What it can do in Honeyhive

These are the ready-made tools your AI employee already has in Honeyhive. It is not limited to them, but it never has to be taught these.

  • Add datapoints to datasetTool to add datapoints to a dataset. Use when you need to append multiple entries with specified input, ground truth, and history mappings.
  • Create Batch Model EventsTool to create multiple model events in a single request. Use when you need to log a batch of event interactions to HoneyHive.
  • Create Batch Tool EventsTool to log a batch of external API calls as tool events. Use when you need to record multiple tool events in one request—use after gathering all event data.
  • Create DatasetTool to create a dataset. Use when you need to initialize a new dataset within a project.
  • Create ToolTool to create a new tool. Use when you need to register a new function or plugin for invocation.
  • Delete DatapointTool to delete a specific datapoint by its ID. Use when you need to remove a datapoint from HoneyHive after confirming its identifier.
  • Delete DatasetTool to delete a dataset by ID. Use when you need to remove a dataset after confirming its ID.
  • End Evaluation RunTool to mark an evaluation run as completed. Use after finishing manual evaluations to update the run status to completed.
  • Get ConfigurationsTool to retrieve a list of configurations. Use when you need to fetch all configurations for a specific project before making changes.
  • Get DatasetsTool to retrieve a list of datasets. Use when you need to fetch datasets for a specific project with optional filters.
  • Get MetricsTool to retrieve all metrics. Use when you need to list metrics for a specific project, after obtaining project context.
  • Get ProjectsTool to retrieve projects. Use when you need to list all available projects.
  • List ToolsTool to list all available Honeyhive tools. Use when you need to discover which functions or plugins are registered for use.
  • Retrieve DatapointTool to retrieve a specific datapoint by its ID. Use when you have a datapoint ID and need its full details.
  • Retrieve DatapointsTool to retrieve a list of datapoints. Use when you need to fetch datapoints for a project with optional filters.
  • Retrieve EventsTool to retrieve events by filters. Use when you need to export events based on filter criteria, date range, and pagination.
  • Retrieve Experiment ResultTool to retrieve the result of a specific experiment run. Use when you need the status, metrics, and datapoint-level details of a completed experiment.
  • Start Evaluation RunTool to initiate an evaluation run using external datasets. Use after selecting a project and events; optionally link a dataset.
  • Start SessionTool to start a new session. Use when you need to initiate a new tracking session and retrieve its sessionid.
  • Update DatapointTool to update a specific datapoint. Use when you need to modify fields of an existing datapoint.
  • Update DatasetTool to update an existing dataset. Use when you need to modify a dataset's details (name, description, datapoints, linked evaluations, or metadata) after confirming its ID.
  • Update EventTool to update an event. Use when updating event details by ID.
  • Update MetricTool to update an existing metric. Use when you need to modify a metric’s properties after creation. Ensure you retrieve the metric first to verify its current state.
  • Update ProjectTool to update a project's name or description. Use when you need to modify an existing project by its ID after creation.
Access, and who is in charge of it

You stay the boss of your Honeyhive 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 Honeyhive 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 Honeyhive is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Honeyhive 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.

See every app

Questions people ask about Honeyhive

Can an AI employee really work inside Honeyhive?
Yes. It signs in to your own Honeyhive 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 Honeyhive?
No. Nothing moves and nothing is replaced. Your records stay in Honeyhive, 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 Honeyhive account?
You paste in a key from your own Honeyhive account. It is kept encrypted, and you can withdraw it from inside Honeyhive 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 Honeyhive?
It has 24 ready-made tools in Honeyhive today, among them Add datapoints to dataset, Create Batch Model Events and Create Batch Tool Events. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Honeyhive 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 Honeyhive 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 Honeyhive?
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 Honeyhive is written down with what it did and when.