Sanaf AI
Start free
AI Agents

Langbase, 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 Langbase 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.

  • AI Agents
  • Connects with a key
  • 10 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 Langbase is

Langbase is a serverless AI developer platform that enables developers to build, collaborate, and deploy AI agents and applications with composable AI infrastructure.

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

How a run works

One message in, the work done in Langbase.

  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 Langbase. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Langbase 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.

10 tools it already has

What it can do in Langbase

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

  • Create a new pipeTool to create a new pipe. use after configuring pipe parameters. returns pipe details including api key and url.
  • Create MemoryTool to create a new memory. use when storing a new memory record in langbase after confirming memory details.
  • Create ThreadTool to create a new conversation thread. use when starting a fresh chat session or grouping messages into a distinct thread.
  • Delete MemoryTool to delete a specific memory. use when you need to permanently remove a stored memory by its name.
  • Get Thread DetailsTool to retrieve details of a specific conversation thread. use when you need the full thread details by its id after confirming its existence.
  • List all pipesTool to list all pipes. use after authentication to retrieve the complete list of pipes.
  • List Documents in MemoryTool to list documents in a specific memory. use when you need to fetch document metadata (and optionally vectors) from a memory after confirming its name. supports pagination via
  • List MemoriesTool to list all memory objects. use when you need to fetch stored memories for context retrieval.
  • List Thread MessagesTool to list all messages in a conversation thread. use after obtaining the thread id to fetch its messages.
  • Split Content into ChunksTool to split content into smaller chunks. use when processing large text segments to fit downstream limits.
Access, and who is in charge of it

You stay the boss of your Langbase 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 Langbase 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 Langbase 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 Langbase 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 Langbase

Can an AI employee really work inside Langbase?
Yes. It signs in to your own Langbase 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 Langbase?
No. Nothing moves and nothing is replaced. Your records stay in Langbase, 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 Langbase account?
You paste in a key from your own Langbase account. It is kept encrypted, and you can withdraw it from inside Langbase 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 Langbase?
It has 10 ready-made tools in Langbase today, among them Create a new pipe, Create Memory 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 Langbase 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 Langbase 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 Langbase?
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 Langbase is written down with what it did and when.